0
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
🛰️ A CLI tool for tracking token usage from OpenCode, Claude Code, 🦞OpenClaw (Clawdbot/Moltbot), Pi, Codex, Gemini, Cursor, AmpCode, Factory Droid, Kimi, and more! • 🏅Global Leaderboard + 2D/3D Contributions Graph
Top fixes
Highest-impact changes first, ranked by point weight
- 1Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
- 2Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 3Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- 4Dependency manifest6pt
Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
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
88
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
84
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.
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (crates/tokscale-cli/tests).
CI is configured (.github/workflows/build-native.yml).
Linter or formatter configured (packages/frontend/eslint.config.mjs).
Project health
92
Dependency manifest found (Cargo.toml).
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)
- 257Forks
- 64Releaseslatest 6mo ago
Community
- -Community health
- -authors own >50% of commits
- 3,908Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 84Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/build-native.yml).
- cratesGood: Test files detected (crates/tokscale-cli/tests).
- docs
- packagesGood: Linter or formatter configured (packages/frontend/eslint.config.mjs).
- scripts
- .gitignoreGood: .gitignore present.
- .npmrc
- AGENTS.md
- bun.lock
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- LICENSEGood: Licensed under MIT.
- package.json
- README.ja.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.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.
- README.ko.md
- README.md
- README.zh-cn.md
- tarpaulin.toml
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/junhoyeo/tokscale)