0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
❄️ my nix modules, overlays, host configurations, and more!
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 B (87).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 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
68
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.
Licensed under MIT.
Engineering
37
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/build.yml).
Lockfile present (docs/bun.lock). Installs are reproducible.
Linter or formatter configured (prettier.config.js).
Project health
100
Dependency manifest found (docs/package.json).
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)
- 5Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 106Watchers
Responsiveness
- 28d 2hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files24 root entries
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Dependabot configured for github-actions.
- docsGood: Lockfile present (docs/bun.lock). Installs are reproducible.Good: Dependency manifest found (docs/package.json).
- examples
- hosts
- mods
- pkgs
- scripts
- secrets
- .envrc
- .gitignoreGood: .gitignore present.
- .prettierignore
- .vale.ini
- AGENTS.md
- default.nix
- flake-compat.nix
- flake.lock
- flake.nix
- home.nix
- ignore
- LICENSEGood: Licensed under MIT.
- overlays.nix
- prettier.config.jsGood: Linter or formatter configured (prettier.config.js).
- 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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- scripts.nix
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/jpetrucciani/nix)