Strong early engineering with some momentum.
Documentation
78
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
84
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.
Lockfile present (bun.lock). Installs are reproducible.
Test files detected (e2e/a11y.spec.ts).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.editorconfig).
Project health
76
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 2Forks
- 22Releaseslatest 1mo ago
Community
- —Community health
- —authors own >50% of commits
- 12Watchers
Responsiveness
- 22hMedian issue response
- —Median PR merge time
- 3Open issues
Repository files26 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- blog
- design
- docs
- e2eGood: Test files detected (e2e/a11y.spec.ts).
- packages
- proposal
- scripts
- tests
- .dependency-cruiser.cjs
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- .prettierrc
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- bunfig.toml
- CLAUDE.md
- codecov.yml
- docker-compose.test.yml
- eslint.config.js
- LICENSEGood: Licensed under Apache-2.0.
- OPENCODE_CONFIG.md
- package.jsonGood: Dependency manifest found (package.json).
- playwright.config.ts
- README.mdGood: 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.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.
- STATE.md
- tsconfig.base.json