0
/ 100
Fresh project with a decent start. Tests and CI now will set it apart.
My extended brain, what you learn is what you note.
Documentation
28
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
Licensed under MIT.
Engineering
69
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/deploy-tago.yml).
Lockfile present (go.sum). Installs are reproducible.
Test files detected (content/en/spec).
Formatting enforced (gofmt (built into Go toolchain)).
Project health
100
Dependency manifest found (go.mod).
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)
- 0Forks
- 57Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 8Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 7Open issues
Repository files17 root entries
- .githubGood: CI is configured (.github/workflows/deploy-tago.yml).
- .wrangler
- contentGood: Test files detected (content/en/spec).
- i18n
- layouts
- scriptsGood: Environment pinned via scripts/translate/.python-version.
- static
- themes
- .gitignoreGood: .gitignore present.
- content-lastmods.json
- deploy-shards.toml
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- hugo.toml
- LICENSEGood: Licensed under MIT.
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- tago.toml