GitHub's Favorite API List Is a Billboard Now

The public-apis repository is on GitHub's trending page again this week, which happens with the regularity of a tide. At 464,000 stars it sits in the same orbit as React and Vue — remarkable for a project that ships no code, just a giant Markdown table of free APIs. Every wave of new developers discovers it, stars it, and moves on. What almost none of them notice is that the community that built the thing walked away years ago, and what they're starring today is, functionally, an ad unit.

Open the README and the first full screen is a banner announcing that the "APILayer Unified Suite is now Live! 🎉", followed by a product table for APILayer's commercial offerings — IPstack, Marketstack, Weatherstack — complete with Postman buttons and UTM-tagged referral links. The actual list of free APIs, the reason anyone ever starred this repo, starts well below the fold.

How a community project became a billboard

Todd Motto started the list in 2015 and handed it to a community organization in 2016, which is where most awesome-list stories end: volunteers merge PRs forever, or the thing quietly dies. This one took a third path. The people who ended up controlling the GitHub org built a commercial API business, APILayer, and in May 2021 the repo's description and README started sprouting links to it.

Then it got uglier. In March 2022, according to a detailed account by then-maintainer Yann Bertrand, the volunteer maintainers had their access silently downgraded, the maintainers list was deleted from the README, and commercial APIs were added to a list whose own contribution guidelines required free-only entries. The maintainers spent months trying to reach anyone at APILayer and got nowhere.

The commit history tells you what happened next, and it's blunt. After mid-2022 the repo went essentially dark: a fourteen-month gap between July 2022 and September 2023, then isolated single commits separated by half a year through 2024 and 2025. The pull request queue swelled to around 1,700 open PRs — years of community submissions nobody was reading. Regular merging only resumed in early 2026, with most recent merges landing through a single account. The revival is real, but it's a company tending its marketing asset, not a community maintaining its resource.

Why it keeps trending anyway

Stars compound. Every "top GitHub repos" listicle, every bootcamp syllabus, every "project ideas for beginners" thread links to public-apis, which drives stars, which drives trending placement, which drives more listicles. GitHub's trending algorithm measures attention, not health — there's no signal on that page for "the maintainers were locked out four years ago" or "nobody checked these links for years."

That last part matters practically. A link list that sat unmerged from 2022 to 2026 has absorbed four years of link rot in an industry where free-tier APIs die constantly — acquired, rug-pulled, or quietly rate-limited into uselessness. The entries carry auth and CORS columns, but nobody was verifying any of it during the gap. If you're grabbing an API from the list for a weekend project, budget a few minutes to confirm the endpoint still answers before you build around it.

What to actually use

The good news is that the fork ecosystem did what fork ecosystems are for. Two successors are worth your bookmark:

• public-api-lists/public-api-lists (15.5k stars) is the community continuation in the original spirit — actively maintained, ad-free, and it exposes the list itself as a free JSON API, which is what a machine-readable directory should have been all along.
• publicapis.dev, backed by Marcel Cruz's actively maintained repo (9.3k stars, commits landing the same day as upstream's), wraps the list in a searchable site with 50+ categories.

Both are a fraction of the original's star count and both are better resources today. That gap — 464k stars pointing at the compromised version, 25k combined pointing at the living ones — is the whole problem with stars as a trust signal in one number.

The lesson for everyone else

The governance failure here is worth internalizing, because it generalizes. An awesome list has no code, so the repo itself is the product — and GitHub org ownership is absolute. The public-apis maintainers had commit rights but not admin rights, which meant every hour they donated was building SEO equity for whoever held the org. When the owners decided to monetize, there was no license to violate (it's MIT, and a list of links barely has copyright to enforce anyway), no trademark to invoke, no recourse except forking and starting the star count from zero.

If you maintain or contribute to a curation project, the checklist is short: know who holds org admin, get governance in writing before you invest serious hours, and treat a corporate owner's "community project" as the marketing channel it will eventually become. If you're a company thinking about doing what APILayer did — it worked, in the narrow sense that the repo still trends and the referral links still get eyeballs. But the maintainers left, the forks are where the actual curation happens, and the flagship asset is a stale list wearing a banner ad. That's the trade.

Meanwhile the tide will keep coming in. public-apis will trend again next month, another hundred thousand developers will star it, and the most useful thing about the page will still be that it leads, eventually, to its own replacements.