Polished and well engineered. Punching above its star count.
Culture Amp's Kaizen Design System :seedling:
Documentation
87
Contributing guide5pt
72
Contributing guide is detailed and thorough.
README12pt
85
README is present.
Install and run instructions9pt
90
README documents how to install the project.
License6pt
100
Licensed under MIT.
Engineering
93
Reproducibility6pt
80
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
CI/CD14pt
83
CI is configured (.github/workflows/check-files.yml).
Tests18pt
100
Test files detected (packages/components/__tests__).
Linting and formatting5pt
100
Linter or formatter configured (.prettierrc.js).
Issue and PR templates6pt
100
Issue or PR templates present.
Project health
89
Dependency manifest6pt
65
Dependency manifest found (package.json).
Repository metadata5pt
100
Repository has a description.
Activity5pt
100
Actively maintained (pushed within the last month).
Housekeeping3pt
100
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 23Forks
- 1000Releaseslatest 3y ago
Community
- —Community health
- —authors own >50% of commits
- 174Watchers
Responsiveness
- 21d 16hMedian issue response
- 2hMedian PR merge time
- 12Open issues
Repository files39 root entries
- .buildkite
- .changeset
- .claude
- .githubGood: CI is configured (.github/workflows/check-files.yml).Good: Issue or PR templates present.
- .vscode
- bin
- docs
- packagesGood: Test files detected (packages/components/__tests__).
- patches
- plop-templates
- .enchiridion.toml
- .envrc
- .gitignoreGood: .gitignore present.
- .npmrc
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierignore
- .prettierrc.jsGood: Linter or formatter configured (.prettierrc.js).
- .stylelintignore
- .stylelintrc-css.mjs
- .stylelintrc-scss.json
- catalog-info.yaml
- CODEOWNERS
- CONTRIBUTING.mdGood: 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
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- plopfile.js
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- process-compose.yaml
- README.mdGood: 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