Good shape overall. A few tweaks would push it into the top tier.
Documentation
81
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 MIT.
Engineering
71
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
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 (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/ci.yml).
Test files detected (src/components/featureInfo/__tests__).
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
- —Commits (30d / 90d)
- 24Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 316Watchers
Responsiveness
- 24d 3hMedian issue response
- <1hMedian PR merge time
- 1Open issues
Repository files25 root entries
- .agents
- .claude
- .codex
- .githubGood: CI is configured (.github/workflows/ci.yml).
- docs
- public
- scripts
- srcGood: Test files detected (src/components/featureInfo/__tests__).
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CLAUDE.md
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- index.html
- LICENSEGood: Licensed under MIT.
- nginx.conf
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- 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.
- tsconfig.app.json
- tsconfig.json
- vite.config.ts
- vitest.config.ts