93
/ 100
Polished and well engineered. Punching above its star count.
A performance-first TypeScript checker
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 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
92
README is present.
README documents how to install the project.
Contributing guide is detailed and thorough.
Licensed under Apache-2.0.
Engineering
91
CI is configured (.github/workflows/ci-health.yml).
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (crates/conformance/tests).
Rust linting configured (cargo clippy in CI).
Issue or PR templates present.
Project health
100
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
- 2997 / 14240Commits (30d / 90d)
- 11Forks
- 27Releaseslatest 2mo ago
Community
- 62% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 513Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 180Open issues
Repository files18 root entries
- .agents
- .cargo
- .claude
- .codex
- .config
- .githubGood: CI is configured (.github/workflows/ci-health.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- .vscode
- cratesGood: Test files detected (crates/conformance/tests).
- docsGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- scriptsGood: Environment pinned via scripts/infra/bench-base/Dockerfile.
- .gitignoreGood: .gitignore present.
- .gitmodules
- AGENTS.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- deny.toml
- LICENSE.txtGood: Licensed under Apache-2.0.
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tsz-org/tsz)