trpc/trpc
Grade a repo

96

/ 100

GradeA

Excellent work. The main thing left to polish is dependency metadata.

Top 5% of 5,156 graded repos

🧙‍♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.

TypeScript40,463MIT6d ago

Outstanding. A score of 96/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    Reproducibility6pt

    Ensure .github/dependabot.yml lists 2+ package-ecosystem entries (e.g. your language plus github-actions).

  2. 2
    Dependency manifest6pt

    Add a one-line description to package.json. It appears in npm search and on GitHub.

  3. 3
    Dependency manifest6pt

    Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.

  4. 4
    Dependency manifest6pt

    Add a `keywords` array to help people find your package on npm.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

97

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

99

Reproducibility6pt92

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (examples/.experimental/next-app-dir/test).

CI/CD14pt100

CI is configured (.github/workflows/check-skills.yml).

Linting and formatting5pt100

Linter or formatter configured (eslint.config.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 1,643
    Forks
  • 239
    Releaseslatest 5y ago

Community

  • 87% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 40,463
    Watchers

Responsiveness

  • 580d
    Median issue response
  • <1h
    Median PR merge time
  • 254
    Open issues
Repository files33 root entries
  • _artifacts
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/check-skills.yml).
    Good: Issue or PR templates present.
  • .superset
  • .vscode
  • examples
    Good: Test files detected (examples/.experimental/next-app-dir/test).
    Good: Environment pinned via examples/next-prisma-websockets-starter/docker-compose.yaml.
    Good: Dependabot is configured. Dependencies update automatically.
  • packages
  • scripts
  • www
  • .coderabbit.yaml
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .kodiak.toml
  • .npmrc
  • .nvmrc
  • .prettierignore
  • .tool-versions
  • .ts-prunerc
  • codecov.yml
  • CONTRIBUTING.md
    Good: 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.js
    Good: Linter or formatter configured (eslint.config.js).
  • lerna.json
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • prettier.config.js
  • README.md
    Good: 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.md
    Good: Security policy present.
  • tsconfig.build.json
  • tsconfig.json
  • turbo.json
  • vitest.config.ts
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/trpc/trpc)](https://www.repo-grade.com/report/trpc/trpc)

More graded TypeScript repos