81
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
The definitive list of the best of (consumer facing) open source.
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 `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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 found.
README documents how to install the project.
Licensed under MIT.
Engineering
73
CI is configured (.github/workflows/format-maintenance.yml).
Test files detected (core/tests).
Lockfile present (core/uv.lock). Installs are reproducible.
Linter or formatter configured (core/ruff.toml).
Issue or PR templates present.
Project health
100
Dependency manifest found (apps/cli/go.mod).
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)
- 126Forks
- 8Releaseslatest 6mo ago
Community
- 100% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 3,279Watchers
Responsiveness
- 12hMedian issue response
- 5hMedian PR merge time
- 10Open issues
Repository files9 root entries
- .githubGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Code of conduct present.Good: CI is configured (.github/workflows/format-maintenance.yml).Good: Issue or PR templates present.Good: Security policy present.
- appsGood: Dependency manifest found (apps/cli/go.mod).
- assets
- coreGood: Test files detected (core/tests).Good: Linter or formatter configured (core/ruff.toml).Good: Lockfile present (core/uv.lock). Installs are reproducible.Good: Environment pinned via core/.python-version.
- resources
- .gitattributes
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under MIT.
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/mustbeperfect/definitive-opensource)