93
/ 100
Excellent work. The last thing to polish is a reproducible setup. Widely used, with the craft to match.
A curated list of awesome Go frameworks, libraries and software
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
88
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
93
Lockfile present (go.sum). Installs are reproducible.
CI is configured (.github/workflows/check-for-spammy-issues.yml).
Test files detected (main_test.go).
Formatting enforced (gofmt (built into Go toolchain)).
Issue or PR templates present.
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
- 40 / 133Commits (30d / 90d)
- 13,408Forks
- 0Releases
Community
- 100% - GoodCommunity health
- -authors own >50% of commits
- 177,763Watchers
Responsiveness
- 1hMedian issue response
- <1hMedian PR merge time
- 190Open issues
Repository files23 root entries
- .githubGood: CI is configured (.github/workflows/check-for-spammy-issues.yml).Good: Issue or PR templates present.
- pkg
- tmpl
- .codeclimate.yml
- .cursorrules
- .dockerignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- COVERAGE.md
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under MIT.
- main_test.goGood: Test files detected (main_test.go).
- main.go
- MAINTAINERS
- maturity_test.go
- netlify.toml
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- stale_repositories_test.go
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/avelino/awesome-go)