kentcdodds/kentcdodds.com

0

/ 100

Documentation83
Engineering68
Health89
MDX2,486Other1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

My personal website

Documentation

83

README12pt55

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

68

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt40

CI is configured (.github/workflows/index-semantic-content.yml).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Tests18pt100

Test files detected (other/__tests__).

Linting and formatting5pt100

Linter or formatter configured (devDependency in package.json).

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)
  • 655
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,486
    Watchers

Responsiveness

  • 9h
    Median issue response
  • 3h
    Median PR merge time
  • 11
    Open issues
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/index-semantic-content.yml).
  • .husky
  • docs
  • other
    Good: Test files detected (other/__tests__).
  • services
    Good: Environment pinned via services/site/Dockerfile.
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .oxlintrc.json
  • .prettierignore
  • AGENTS.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • fly.toml
  • LICENSE.md
    Good: Licensed under Other.
  • lint-staged.config.cjs
  • nx.json
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • tsconfig.base.json