imbhargav5/rooks
Grade a repo

0

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

Over 890k monthly downloads. Collection of awesome react hooks

Documentation92
Engineering85
Health92
TypeScript3,443MITtoday

Documentation

92

Contributing guide5pt66

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

85

CI/CD14pt57

CI is configured (.github/workflows/ci-release.yml).

Reproducibility6pt80

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

Tests18pt100

Test files detected (packages/rooks/src/__tests__).

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.js).

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

  • -
    Commits (30d / 90d)
  • 220
    Forks
  • 220
    Releaseslatest 6y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 3,443
    Watchers

Responsiveness

  • 5d 21h
    Median issue response
  • 2h
    Median PR merge time
  • 77
    Open issues
Repository files40 root entries
  • .changeset
  • .claude
  • .codesandbox
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/ci-release.yml).
    Good: Issue or PR templates present.
  • .husky
  • .ralph
  • .unbound
  • .vscode
  • apps
  • data
  • i18n
  • packages
    Good: Test files detected (packages/rooks/src/__tests__).
  • scripts
  • static
  • template
  • .all-contributorsrc
  • .cspell.json
  • .eslintignore
  • .eslintrc.js
    Good: Linter or formatter configured (.eslintrc.js).
  • .gitignore
    Good: .gitignore present.
  • .mergify.yml
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .oneignore
  • .prettierignore
  • .prettierrc.json
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • code-style-guide.md
  • 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.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • GEMINI.md
  • ideas.md
  • LICENSE
    Good: Licensed under MIT.
  • MAINTENANCE.md
  • 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.cjs
  • 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.
  • turbo.json