95
/ 100
Excellent work. The main thing left to polish is CI.
🤖 A client-first, server-capable, fully type-safe router and full-stack framework for the web (React and more).
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 a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
94
README is present.
README documents how to install the project.
Licensed under MIT.
Contributing guide is detailed and thorough.
Engineering
88
CI is configured (.github/workflows/check-skills.yml).
Test files detected (benchmarks/client-nav/link-performance/config.test.ts).
Linter or formatter configured (e2e/e2e-utils/eslint.config.js).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Issue or PR templates present.
Project health
92
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)
- 1,898Forks
- 1000Releaseslatest 4mo ago
Community
- 62% - FairCommunity health
- -authors own >50% of commits
- 15,223Watchers
Responsiveness
- 2hMedian issue response
- 1hMedian PR merge time
- 768Open issues
Repository files38 root entries
- _artifacts
- .agents
- .changeset
- .devcontainer
- .githubGood: CI is configured (.github/workflows/check-skills.yml).Good: Renovate is configured (.github/renovate.json). Dependencies update automatically across every package manager it detects.Good: Issue or PR templates present.
- .nx
- benchmarksGood: Test files detected (benchmarks/client-nav/link-performance/config.test.ts).
- docs
- e2eGood: Linter or formatter configured (e2e/e2e-utils/eslint.config.js).
- examples
- gpt
- media
- packages
- scripts
- skills
- .coderabbit.yaml
- .gitattributes
- .gitignoreGood: .gitignore present.
- .npmrc
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierignore
- AGENTS.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- DEBUGGING.md
- eslint.config.js
- how-to-guides-implementation-plan.md
- how-to-testing-plan.md
- knip.json
- labeler-config.yml
- LICENSEGood: Licensed under MIT.
- nx.json
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- prettier.config.js
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- top-10-how-to-guides.md
- tsconfig.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/tanstack/router)