94

/ 100

GradeA

Excellent work. The main thing left to polish is a contributing guide.

Top 7% of 5,156 graded repos

The library for web and native user interfaces.

JavaScript246,708MIT8d ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  2. 2
    Reproducibility6pt

    Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.

  3. 3
    Dependency manifest6pt

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

  4. 4
    Dependency manifest6pt

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

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

90

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

99

Reproducibility6pt92

Lockfile present (yarn.lock). Installs are reproducible.

Tests18pt100

Test files detected (.claude/skills/test).

CI/CD14pt100

CI is configured (.github/workflows/compiler_rust.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

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

  • 85 / 158
    Commits (30d / 90d)
  • 51,163
    Forks
  • 132
    Releaseslatest 12y ago

Community

  • 100% - Good
    Community health
  • 6 bus factor
    authors own >50% of commits
  • 246,708
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 3h
    Median PR merge time
  • 1,222
    Open issues
Repository files36 root entries
  • .claude
    Good: Test files detected (.claude/skills/test).
  • .codesandbox
  • .github
    Good: CI is configured (.github/workflows/compiler_rust.yml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • compiler
  • fixtures
  • flow-typed
  • packages
  • scripts
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .eslintignore
  • .eslintrc.js
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierignore
  • .prettierrc.js
  • .watchmanconfig
  • babel.config-react-compiler.js
  • babel.config-ts.js
  • babel.config.js
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    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).
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • dangerfile.js
  • flow-typed.config.json
  • LICENSE
    Good: Licensed under MIT.
  • MAINTAINERS
  • package.json
    Good: Dependency manifest found (package.json).
  • react.code-workspace
  • ReactVersions.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.
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.
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/facebook/react)](https://www.repo-grade.com/report/facebook/react)

More graded JavaScript repos