sindresorhus/awesome is the root index of the “awesome” movement: not a list about one topic, but the list of lists. Created in 2014 and sitting near half a million stars, it points to roughly 700 curated lists across categories like Programming Languages, Front-End, Security, Databases, and Books. If you only read the README, you see links. The thing worth understanding is the machinery and the rules underneath, because that is what makes this index trustworthy where a topic tag dump is not.
Why this is more than a link dump
Anyone can collect links. What sindresorhus/awesome did was turn curation into a governed process, and that governance is the actual product. Three rules carry most of the weight:
- A submitted list must have existed for at least 30 days before it can be added. No same-day shells.
- The PR author must review at least four other open PRs, and not with “looks good”: they have to point out concrete problems. Submission funds maintenance.
- A list must be CC0 (or another Creative Commons license), carry the awesome badge linking back to the root, include a contribution guide, and pass awesome-lint with no errors.
The philosophy is stated bluntly in the project’s manifesto: “only awesome is awesome.” When in doubt, leave it out. That bar is why being listed here functions as a credibility signal across the ecosystem.
How to actually use it
The README is large, so navigate it rather than scroll it.
- Use the short domain
awesome.reas the canonical entry point. Ctrl+Fthe category names to jump.- Third-party tools like Awesome Search and Track Awesome List index and monitor lists across the ecosystem.
Treat the index as a directory, not an endorsement of any single list’s current quality. Which leads to the honest caveats.
The honest caveats
Two long-running tensions are worth knowing before you rely on it.
First, unmaintained lists. The index links to lists, not to their freshness. A long-open request (#3642) asks for a way to flag deprecated or unmaintained lists, and it remains unresolved. Some destinations you click will be stale, and the root index will not warn you.
Second, the AI-slop problem. As generated content floods open source, the project has moved to auto-close low-effort PRs (#4165), but the line between “AI-generated list” (rejected) and “AI-assisted human curation” (allowed) is not crisp. A 2026 thread (#4094) captured the friction: a curator who used an AI agent only to pass the linter was rejected and asked for a clearer policy. The governance that made awesome trustworthy is now being stress-tested by tooling it was not designed for.
Who maintains it and why that matters
The list is the work of Sindre Sorhus, one of the most prolific open-source authors alive, and that lineage explains the standards. He did not just create an index; he exported its conventions (the badge spec, awesome-lint, the contribution template) to the whole community. The CC0 license is a deliberate statement: the index itself carries no copyright wall. This is a soft-power case study as much as a list.
How it compares
| Repo | What it is | Note |
|---|---|---|
| sindresorhus/awesome | Root meta-index of lists | The directory of directories |
| public-apis/public-apis | One topic: free APIs | Huge single-domain list |
| awesome-selfhosted | One topic: self-hosted apps | Huge single-domain list |
| codecrafters-io/build-your-own-x | Curated build-it tutorials | Topical, not a meta-index |
public-apis and awesome-selfhosted are massive single-topic lists; build-your-own-x is a focused tutorial collection. sindresorhus/awesome is the only one of the four that indexes the others rather than competing on a topic.
When it fits, and when it does not
It fits as a starting point when you are entering an unfamiliar domain and want a human-curated jumping-off list. It does not fit as a quality guarantee or a freshness signal: verify the destination list is maintained before trusting it. Use it to find candidates, not to end the search.
FAQ
Is sindresorhus/awesome the most starred repo on GitHub? It is among the very top, sitting near half a million stars as the root index of the awesome-list movement. A few single-topic lists like public-apis are in the same range.
How many lists are in sindresorhus/awesome? Roughly 700 curated lists across categories from Programming Languages to Security to Books, each meeting the inclusion bar at submission time.
Is being listed in awesome a mark of quality? It means the list passed the inclusion bar at submission time and is CC0 with a contribution guide. It does not certify the linked resources are still good.
Can I submit my own list? Yes, after it has lived 30 days, passes awesome-lint, carries the badge, and you review four other PRs with substantive feedback.
Related reading
For curated, build-it learning resources see codecrafters-io/build-your-own-x. If you are exploring how communities encode standards into tooling, the skills ecosystem in anthropics/skills is a modern parallel.