Just launched. Good start. Add tests and CI early.
Documentation
46
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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 documents how to install the project.
README is present.
Engineering
80
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 (pnpm-lock.yaml). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Test files detected (src/App.spec.tsx).
Linter or formatter configured (.prettierrc).
Project health
73
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
- 25 / 25Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- 14% - WeakCommunity health
- —authors own >50% of commits
- 0Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- docs
- public
- srcGood: Test files detected (src/App.spec.tsx).
- tests
- .gitignoreGood: .gitignore present.
- .nvmrcGood: Environment pinned via .nvmrc.
- .prettierignore
- .prettierrcGood: Linter or formatter configured (.prettierrc).
- eslint.config.js
- index.html
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- tsconfig.app.json
- tsconfig.json
- tsconfig.node.json
- vite.config.ts