chakra-ui/chakra-ui
Grade a repo

93

/ 100

GradeA

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 6% of 5,156 graded repos

Chakra UI is a component system for building SaaS products with speed ⚡️

Documentation93
Engineering98
Health92
TypeScript40,478MIT1mo ago

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

Top fixes

Highest-impact changes first, ranked by point weight

9 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 .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  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 `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

93

Contributing guide5pt71

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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

98

Reproducibility6pt80

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

Tests18pt100

Test files detected (packages/cli/__tests__).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

92

Dependency manifest6pt75

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

  • 29 / 94
    Commits (30d / 90d)
  • 3,619
    Forks
  • 1000
    Releaseslatest 3y ago

Community

  • 87% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 40,478
    Watchers

Responsiveness

  • 5h
    Median issue response
  • 3h
    Median PR merge time
  • 16
    Open issues
Repository files36 root entries
  • .changelog
  • .changeset
  • .claude
  • .github
    Good: CI is configured (.github/workflows/quality.yml).
    Good: Issue or PR templates present.
  • .husky
  • .storybook
  • .vscode
  • apps
  • media
  • packages
    Good: Test files detected (packages/cli/__tests__).
  • sandbox
    Good: Environment pinned via sandbox/react-router/Dockerfile.
  • scripts
  • skills
  • .all-contributorsrc
  • .commitlintrc
  • .gitignore
    Good: .gitignore present.
  • .lintstagedrc
  • .npmrc
  • .nvmrc
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • eslint.config.mjs
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • renovate.json
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.build.json
  • tsconfig.json
  • vite.config.ts
  • vitest.setup.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/chakra-ui/chakra-ui)](https://www.repo-grade.com/report/chakra-ui/chakra-ui)

More graded TypeScript repos