0
/ 100
Solid engineering. The main gap is visibility.
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.
- 2README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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.
A license file is present.
Engineering
80
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
Test files detected (raku-doc/doc/Type/IO/Spec).
Lockfile present (Cargo.lock). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Issue or PR templates present.
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (Cargo.toml).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 1Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 5Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 11Open issues
Repository files34 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- benchmarks
- docs
- news
- old-design-docsGood: A license file is present.
- raku-docGood: 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: Test files detected (raku-doc/doc/Type/IO/Spec).Good: Issue or PR templates present.
- roast
- scripts
- src
- t
- tests
- todo
- TODO_roast
- tools
- wasm-demo
- -
- .gitignoreGood: .gitignore present.
- .mise.tomlGood: Environment pinned via .mise.toml.
- .tagpr
- AGENTS.md
- ANALYSIS.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CLAUDE.md
- HISTORY-pass.svg
- HISTORY.tsv
- lefthook.yml
- Makefile
- mise.toml
- PERFORMANCE.md
- PLAN.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.
- roast-whitelist.txt
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tokuhirom/mutsu)