Open-source project
avelino/awesome-go avatar
avelino/awesome-go

Awesome Go: A Curated Map of the Go Ecosystem, Not a Package Manager

GitHub describes it as A curated list of awesome Go frameworks, libraries and software. The repository metadata lists Go as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

194,087 stars13,749 forksGoMIT

At a glance

What is it?
Awesome Go is a hand-maintained list of Go frameworks, libraries, and software, organized into dozens of categories. It is a discovery tool, not a dependency manager, and its value depends entirely on the quality of its curation.
Who is it for?
Adopt Awesome Go if you are a Go developer who wants a broad, community-vetted starting point for library discovery, especially when exploring unfamiliar problem domains. Do not treat it as a definitive quality ranking or a substitute for checking a library's own maintenance status, license, and API stability.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly Go, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • avelino/awesome-go194,087 ★ · +13,123
Star history
Repository2026-08-132026-11-15
avelino/awesome-go181k194.1k

13,123 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What This List Solves and Who It Serves

The Go ecosystem has grown beyond what any single developer can track. Awesome Go addresses that by grouping hundreds of projects into a single, categorized index. The README describes it as "A curated list of awesome Go frameworks, libraries, and software," clearly inspired by awesome-python. It serves engineers who need to find a library for a specific task, whether that is an ORM, a web framework, a UUID generator, or a machine learning toolkit. The target audience is broad: anyone writing Go who wants to avoid reinventing common components. It is not a package manager or a dependency resolver. It is a discovery layer, a starting point for research. The list's structure, with its many subcategories, makes it easy to jump straight to a domain without wading through unrelated projects.

How the List Is Organized and Maintained

The list lives in a README that is meticulously structured, next to a small Go module (main.go, tmpl/, pkg/). The contents section expands into a hierarchy that covers everything from Actor Model to WebAssembly. Categories are subdivided aggressively. For example, Data Structures and Algorithms has thirteen subcategories, including Bloom and Cuckoo Filters, Nullable Types, and Pipes. This granularity is a key feature. It lets a developer find a highly specific solution, such as a bit set or a text analysis tool, without scanning a flat list of hundreds of entries. The maintenance model is community-driven. The README explicitly asks contributors to follow contribution guidelines and to submit pull requests if a package is no longer maintained or is not a good fit. This means the list is only as current as its contributors make it. The project also runs tests via GitHub Actions, as seen in the badge links, but those tests likely check the list's formatting and links, not the quality of the listed libraries.

Getting Started and Contributing

There is no installation step. The list lives at awesome-go.com and in the GitHub repository. To use it, you browse the categories or search the README. To contribute, you read the CONTRIBUTING.md file first, then submit a pull request. The README gives a clear instruction: "If you see a package or project here that is no longer maintained or is not a good fit, please submit a pull request to improve this file." This is the entire workflow. The project also has a Slack channel on the Golang Bridge, with a link to join. This makes the contribution process social, but it is not required to participate. For a typical user, the interaction is read-only: visit the site, find a library, click through to its repository.

The Real Limitation: Curation Is Not Verification

The core weakness of Awesome Go is that inclusion does not imply endorsement of quality or maintenance status. The list is curated, but the curation is subjective and depends on the vigilance of contributors. A library can sit in the list long after it has been abandoned. The README's own request to submit pull requests for unmaintained projects is an admission of this. For an engineer making a critical dependency choice, this list is only a filter, not a verdict. It can point you to options, but you must still verify each candidate yourself. The list also has no versioning for its own content. The repository's default branch is main, and there are no recent releases, which means the list changes continuously without stable snapshots. If you rely on a specific version of the list for reproducibility, you cannot get it. This is acceptable for a discovery tool, but it is a real constraint.

Alternatives: Package Registries and Search Engines

The closest alternative to Awesome Go is not another list, but the Go package index at pkg.go.dev. That site provides metadata such as version history, license, and documentation for every published Go module. It is not curated by humans in the same way, but it offers factual data that Awesome Go lacks. Another alternative is a plain search engine query, which can surface recent blog posts and discussions that reflect current community sentiment. The difference in approach is fundamental. Awesome Go is a human-curated editorial layer, whereas pkg.go.dev is an automated registry. If you want a broad survey, Awesome Go wins. If you need to check a specific library's maintenance status or API changes, pkg.go.dev is the better tool. The two complement each other, but they are not interchangeable. An engineer should use both, starting with the list for discovery and then moving to the registry for verification.

Maintenance, Licensing, and Upgrade Cost

The repository itself is licensed under MIT, which means the list content can be reused freely, but this does not apply to the libraries it references. Each listed project carries its own license, and the list does not summarize those licenses. You must check each one. The maintenance cost of the list is low for users, but the real cost is the time you spend evaluating entries. There is no upgrade path because there is no software to upgrade. The list changes constantly, and you do not need to track those changes unless you are adding new entries. For contributors, the cost is higher: you must follow the contribution guidelines and engage with the pull request process. The project's sponsorship model, which the README describes as having no monthly fee but using money raised to repay the people who keep it running, suggests that ongoing maintenance depends on community support. This is a volunteer-driven project, and its continuity is not guaranteed.

Editorial conclusion

Adopt Awesome Go if you are a Go developer who wants a broad, community-vetted starting point for library discovery, especially when exploring unfamiliar problem domains. Do not treat it as a definitive quality ranking or a substitute for checking a library's own maintenance status, license, and API stability. Before using any listed project, verify its last commit date, its license compatibility with your project, and whether it still fits your specific requirements, because the list itself provides no guarantees beyond a contribution process. The site is a useful index, but the final decision on any library remains yours.

Frequently asked questions

How do I add a Go library to awesome-go?

The readme sends contributors to the contribution guidelines in CONTRIBUTING.md and asks for a pull request whenever a listed package is no longer maintained or is not a good fit.

Is awesome-go free to use?

The readme states that Awesome Go has no monthly fee and that the billing and distribution calculations are open to the entire community. It also says there are employees working to keep the list running, and it links a supporter contact address alongside the sponsor table.

How is awesome-go different from awesome-python?

The readme says the list is inspired by awesome-python and links the sindresorhus/awesome list it belongs to. awesome-go also differs in construction: the tree is a Go module with main.go, tmpl/, pkg/, and go.mod at the top level, and the site is published at awesome-go.com through netlify.toml.

Does awesome-go remove dead projects?

The readme asks readers to submit a pull request when a package is no longer maintained or is not a good fit, and the tree carries stale_repositories_test.go next to maturity_test.go. The repository publishes no GitHub releases, so there is no version history to compare a removal against.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/avelino-awesome-go.svg)](https://hysenlabs.com/projects/avelino-awesome-go)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/avelino-awesome-go.svg)](https://hysenlabs.com/projects/avelino-awesome-go)

Was this useful?