Good shape overall. A few tweaks would push it into the top tier.
Documentation
70
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
77
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.
CI is configured (.github/workflows/release.yml).
Lockfile present (go.sum). Installs are reproducible.
Test files detected (adminui/src/components/__tests__).
Formatting enforced (gofmt (built into Go toolchain)).
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 (go.mod).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 19Forks
- 9Releaseslatest 1mo ago
Community
- —Community health
- —authors own >50% of commits
- 113Watchers
Responsiveness
- —Median issue response
- 13hMedian PR merge time
- 0Open issues
Repository files22 root entries
- .codex
- .githubGood: CI is configured (.github/workflows/release.yml).
- adminuiGood: Test files detected (adminui/src/components/__tests__).
- cmd
- docs
- e2e
- examples
- pkg
- plugins
- scripts
- testsupport
- wrappers
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- DockerfileGood: Environment pinned via Dockerfile.
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under Apache-2.0.
- Makefile
- NOTICE
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.