Getting some notice. Tests and CI would be the fastest wins.
A local dev tool where your agents are weird alien dogs. Would you let them in?
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 Other.
Engineering
50
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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 (frontend/package-lock.json). Installs are reproducible.
Test files detected (tests).
Linter or formatter configured (frontend/eslint.config.js).
Project health
96
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 1Forks
- 1Releaseslatest 27d ago
Community
- —Community health
- —authors own >50% of commits
- 20Watchers
Responsiveness
- 5d 3hMedian issue response
- <1hMedian PR merge time
- 11Open issues
Repository files15 root entries
- docs
- frontendGood: Linter or formatter configured (frontend/eslint.config.js).Good: Lockfile present (frontend/package-lock.json). Installs are reproducible.
- hooks
- scripts
- src
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- bootstrap.py
- BUILD.md
- LICENSEGood: Licensed under Other.
- Makefile
- MANIFEST.in
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- 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.
- SECURITY.mdGood: Security policy present.