What's it for
The README, boiled down.
- ▸Go package/library discovery
- ▸category-organized curated index
- ▸community-maintained ecosystem census
Audited from a 0k-token evidence dossier; 0 files read, 9 probes answered.
avelino/awesome-go is the category-defining curated index of Go libraries and tools, organized by topic with mechanically enforced contribution standards [21]. At 178k stars it functions as a default discovery surface for the Go ecosystem [19].
The central tension is between the letter of CONTRIBUTING.md's stated quality bar and what actually clears review: PR merges lean almost entirely on automated CI checks rather than human review [20], and the AI category sampled here reads more like an unfiltered project feed than a curated shortlist [19].
The main knocks:
- The biggest knock is curation dilution in newer categories. The sampled Artificial Intelligence section is dense with near-identical, low-track-record entries carrying promotional phrasing, which is exactly what the archetype's maturity axis penalizes: dead-weight entries slipping past the stated bar [19][2].
- Review rigor on merges is thin. Only 5% of sampled merged PRs carried a review even though 98% came from external authors, so the automated PR quality-check workflow is doing most of the actual vetting rather than a maintainer [20][21].
- Issue-tracker evidence barely supports a health read. 29% of open issues are stale past 180 days, and the underlying sample is too small (one first-response, zero closes) to say much more than that stale tickets accumulate [20].
What holds up:
- Contribution mechanics are unusually well-specified and CI-enforced. A dedicated PR quality-check workflow gates README changes automatically, backing the written CONTRIBUTING.md bar with an actual mechanical check rather than trust alone [21].
- Governance paperwork is complete. Code of Conduct, CONTRIBUTING guide, PR template, and MIT license are all present, and the community profile score reads 100% [20].
- The list is demonstrably active, not abandoned. The last commit landed two days before this audit and 174 PRs sit open, indicating a steady stream of contributor throughput [20][19].
A well-governed, actively tended list whose newest categories show the curation bar slipping.
Compare against pkg.go.dev search/rankings or Go Report Card for library quality signals not dependent on submission curation.
Scorecard
| The idea | ||||
| Conceptis the idea right | 7.5 | — | A | |
| Usefulnessdoes it solve a real problem | 7.5 | — | A | |
| Ergonomicshow it feels to use | 7.0 | — | A | |
| The trajectory | ||||
| Maturityis it battle-tested | 5.0 | — | BB | |
| Longevitywill it matter in 3 years | 7.5 | — | A | |
| Opennesslicense, governance, contributability | 6.0 | — | BBB | |
| The practicals | ||||
| Setup frictioninstall to first success | — | N/Adocs-or-list archetype: no install/config path to trace, the audited artifact is the list itself, not a consumable package. | ||
| Issue healthwill your bug get seen | 4.5 | — | B | |
| Supply-chain hygienecan you trust the pipeline | — | N/Adocs-or-list weight profile: no dependency/build pipeline for the audited artifact; the generator tool's go.mod is incidental tooling, not the list. | ||
| Hype vs. substancedoes the README tell the truth | 6.5 | — | BBB | |
Roll-ups
Useful for
REACH FOR IT WHEN
- ✓Scanning for an established, widely-used Go library in a mature category such as auth or blockchain
- ✓Getting a first census of what exists in a Go subdomain before deeper individual research
LOOK ELSEWHERE WHEN
- →You need every listed entry to have been vetted for quality or active maintenance
cross-check candidate libraries individually against their own health and CVE signals rather than treating inclusion here as an endorsement
23 files read · structure mapped: 94 files · dossier: 7903 tok · complete files: 0 · whole-function: 0 · probes: 9