97
/ 100
Excellent work. The main thing left to polish is dependency metadata.
🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.
Outstanding. A score of 97/100 puts this repo in a very small tier of truly well-engineered projects.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Dependency manifest6pt
Add a one-line description to package.json. It appears in npm search and on GitHub.
- 2Dependency manifest6pt
Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
- 3Dependency manifest6pt
Add a `keywords` array to help people find your package on npm.
- 4Dependency manifest6pt
Add a `homepage` field pointing to your docs or project website.
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
97
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
100
Test files detected (examples/.experimental/next-app-dir/test).
CI is configured (.github/workflows/check-skills.yml).
Linter or formatter configured (eslint.config.js).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
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
- 64 / 101Commits (30d / 90d)
- 1,712Forks
- 240Releaseslatest 5y ago
Community
- 87% - GoodCommunity health
- 2 bus factorauthors own >50% of commits
- 40,719Watchers
Responsiveness
- 580dMedian issue response
- <1hMedian PR merge time
- 179Open issues
Repository files35 root entries
- _artifacts
- .cursor
- .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.
- .superset
- .vscode
- examplesGood: Test files detected (examples/.experimental/next-app-dir/test).Good: Environment pinned via examples/next-prisma-websockets-starter/docker-compose.yaml.
- packages
- patches
- scripts
- www
- .coderabbit.yaml
- .dockerignore
- .gitignoreGood: .gitignore present.
- .kodiak.toml
- .nvmrc
- .prettierignore
- .tool-versions
- .ts-prunerc
- codecov.yml
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.Good: Contributing guide includes code examples.
- eslint.config.jsGood: Linter or formatter configured (eslint.config.js).
- lerna.json
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- paseo.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.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.
- SECURITY.mdGood: Security policy present.
- tsconfig.build.json
- tsconfig.json
- turbo.json
- vitest.config.ts
- vitest.shared.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/trpc/trpc)