79
/ 100
Solid engineering. The biggest lever is CI.
The Void source packages collection
Top 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
82
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under Other.
Engineering
68
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
CI is configured (.github/workflows/build.yaml).
Test files detected (srcpkgs/backblaze-b2/files/test_b2_command_line.py).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (srcpkgs/rubber/files/setup.cfg).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 638 / 2723Commits (30d / 90d)
- 2,746Forks
- 0Releases
Community
- 62% - FairCommunity health
- 9 bus factorauthors own >50% of commits
- 3,379Watchers
Responsiveness
- 10hMedian issue response
- 4d 2hMedian PR merge time
- 1,291Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/build.yaml).Good: Issue or PR templates present.
- commonGood: Licensed under Other.
- etc
- srcpkgsGood: Test files detected (srcpkgs/backblaze-b2/files/test_b2_command_line.py).Good: Dependency manifest found (srcpkgs/rubber/files/setup.cfg).
- .dockerignore
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mailmap
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- COPYING
- Manual.md
- 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.
- xbps-src
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/void-linux/void-packages)