vercel/swr
Grade a repo

85

/ 100

GradeB

Well engineered. The main gaps are setup instructions and a reproducible setup.

Top 22% of 5,156 graded repos

React Hooks for Data Fetching

Documentation65
Engineering92
Health100
TypeScript32,429MIT24d ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    README12pt

    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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

65

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt90

README is present.

License6pt100

Licensed under MIT.

Engineering

92

Reproducibility6pt70

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

CI/CD14pt85

CI is configured (.github/workflows/test-canary.yml).

Tests18pt100

Test files detected (jest.config.js).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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

  • 10 / 15
    Commits (30d / 90d)
  • 1,361
    Forks
  • 129
    Releaseslatest 6y ago

Community

  • 100% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 32,429
    Watchers

Responsiveness

  • 1h
    Median issue response
  • <1h
    Median PR merge time
  • 210
    Open issues
Repository files26 root entries
  • _internal
  • .codesandbox
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/test-canary.yml).
    Good: Issue or PR templates present.
    Good: Security policy present.
  • .husky
  • examples
  • immutable
  • infinite
  • mutation
  • scripts
  • src
  • subscription
  • test
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .oxfmtrc.json
  • .oxlintrc.json
  • .swcrc
  • jest.config.build.js
  • jest.config.js
    Good: Test files detected (jest.config.js).
  • 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
  • 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.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • tsconfig.json
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/vercel/swr)](https://www.repo-grade.com/report/vercel/swr)

More graded TypeScript repos