avelino/awesome-go

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.