50
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Sample projects demonstrating use of scikit-build
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (76).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
52
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Engineering
64
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Test files detected (projects/core-cython-hello/tests).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (ruff.toml).
Project health
100
Dependency manifest found (projects/core-c-hello/pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 29Forks
- 0Releases
Community
- 25% - WeakCommunity health
- 2 bus factorauthors own >50% of commits
- 82Watchers
Responsiveness
- 17d 10hMedian issue response
- 10d 16hMedian PR merge time
- 6Open issues
Repository files9 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- projectsGood: Test files detected (projects/core-cython-hello/tests).Good: Dependency manifest found (projects/core-c-hello/pyproject.toml).
- .gitignoreGood: .gitignore present.
- .pre-commit-config.yaml
- AGENTS.md
- noxfile.py
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.Good: README links to a live demo or deployed app.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- requirements-test.txt
- ruff.tomlGood: Linter or formatter configured (ruff.toml).
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/scikit-build/scikit-build-sample-projects)