Polished and well engineered. Punching above its star count.

Culture Amp's Kaizen Design System :seedling:

Documentation

87

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

93

Reproducibility6pt80

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

CI/CD14pt83

CI is configured (.github/workflows/check-files.yml).

Tests18pt100

Test files detected (packages/components/__tests__).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc.js).

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

  • Commits (30d / 90d)
  • 23
    Forks
  • 1000
    Releaseslatest 3y ago

Community

  • 62% - Fair
    Community health
  • 5 bus factor
    authors own >50% of commits
  • 174
    Watchers

Responsiveness

  • 21d 16h
    Median issue response
  • 2h
    Median PR merge time
  • 13
    Open issues
Repository files39 root entries
  • .buildkite
  • .changeset
  • .claude
  • .github
    Good: CI is configured (.github/workflows/check-files.yml).
    Good: Issue or PR templates present.
  • .vscode
  • bin
  • docs
  • packages
    Good: Test files detected (packages/components/__tests__).
  • patches
  • plop-templates
  • .enchiridion.toml
  • .envrc
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .prettierignore
  • .prettierrc.js
    Good: Linter or formatter configured (.prettierrc.js).
  • .stylelintignore
  • .stylelintrc-css.mjs
  • .stylelintrc-scss.json
  • catalog-info.yaml
  • CODEOWNERS
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide includes code examples.
  • DESIGN.md
  • devbox.json
  • devbox.lock
  • eslint.config.js
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • plopfile.js
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • process-compose.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.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • renovate.json5
  • tsconfig.json
  • turbo.json
  • vite.config.ts
  • vitest.setup.ts