0
/ 100
A well-known project done right. Strong docs and solid engineering throughout.
The utility-first CSS lib for type-safe design systems. No runtime injection, no class soup, no specificity wars—just predictable styling with atomic CSS variables.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
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
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
93
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
CI is configured (.github/workflows/build.yaml).
Test files detected (packages/@tokenami-css/src/compose.test.ts).
Linter or formatter configured (devDependency in package.json).
Issue or PR templates present.
Project health
89
Dependency manifest found (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)
- 11Forks
- 58Releaseslatest 2y ago
Community
- -Community health
- -authors own >50% of commits
- 1,016Watchers
Responsiveness
- 67d 5hMedian issue response
- <1hMedian PR merge time
- 14Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/build.yaml).Good: Issue or PR templates present.
- .vscode
- examples
- packagesGood: Test files detected (packages/@tokenami-css/src/compose.test.ts).
- visual-tests
- .gitignoreGood: .gitignore present.
- .npmrc
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierignore
- CHANGELOG.md
- lerna.json
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- README.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.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.
- tsconfig.json
- turbo.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tokenami/tokenami)