Discofork
Repository brief

avelino/awesome-go

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T22:06:33.525Z
3mo ago

avelino/awesome-go

`avelino/awesome-go` is a large, actively maintained curated index of Go frameworks, libraries, and software rather than a traditional application library. It has very high adoption signals, with 168,571 stars and 13,099 forks, and it was updated on 2026-03-29. The repository is built in Go and centers on list curation, site generation, and maintenance workflows.

GitHub
Loading tags...
Stars168,571
Forks13,099
Default branchmain
Last pushed2026-03-29T22:01:02Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Prefer upstream unless you specifically want a mostly unchanged snapshot. This fork offers no visible added capability, while its 103-commit lag means adopters will likely miss recent curation and maintenance updates.

Choose the fork only if you want an older, customized snapshot. For most adopters, upstream is the better default because it is far more current, better maintained, and much richer in recent Go ecosystem coverage.

Choose this fork only if you want its older, customized Awesome Go variant. For anyone wanting the latest curation, maintenance, and site behavior, upstream is the better default.

Choose this fork only if you want an old, highly customized snapshot and are willing to maintain it yourself. For anyone wanting an up-to-date Awesome Go index or easy upstream adoption, the upstream repository is the better choice.

Choose this fork only if you want a customized, older derivative of Awesome Go and are willing to own the maintenance gap. If you want the latest curated Go index and active upstream workflows, upstream is the better default.

Choose this fork only if you need a custom, legacy Awesome Go base and are willing to maintain it yourself. For most adopters, upstream is the better default because this fork is materially stale and substantially diverged.