0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
N64 Game-Engine and Editor using libdragon & tiny3d
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
72
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
77
CI is configured (.github/workflows/docs.yml).
Lockfile present (docs/requirements.txt). Installs are reproducible.
Test files detected (n64/tests).
Linter or formatter configured (.editorconfig).
Issue or PR templates present.
Project health
100
Dependency manifest found (docs/requirements.txt).
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)
- 135Forks
- 8Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 3,160Watchers
Responsiveness
- 11hMedian issue response
- 7hMedian PR merge time
- 22Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/docs.yml).Good: Issue or PR templates present.
- data
- docsGood: Lockfile present (docs/requirements.txt). Installs are reproducible.Good: Dependency manifest found (docs/requirements.txt).
- n64Good: Test files detected (n64/tests).
- packaging
- scripts
- src
- tools
- vendored
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitmodules
- CMakeLists.txt
- CMakePresets.json
- LICENSEGood: Licensed under MIT.
- Readme.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.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/hailtododongo/pyrite64)