GitHub restricted public access to stargazer lists

On July 23 2026 GitHub cut off the one API StarMapper is built on: the public stargazers list. I've spent the weeks since figuring out what to do about it. Here's where that landed, and four ways it can go next.

What broke

On June 30 2026 GitHub announced restrictions on public API endpoints and UI views. Since July 23 the restriction reached the stargazers list: the GraphQL connection, the REST endpoint and the github.com/owner/repo/stargazers page all return empty or 404, for everyone, on every repo.

StarMapper builds its map from that exact list, who starred a repo and where they live. Without it, a fresh scan finds no one to place. This is a GitHub-side decision, not a bug on our end, and there is currently no API that returns the same data.

Any visitor requests a scan
        │
        ▼
GET github.com/{owner}/{repo}/stargazers
        │
        ├── before Jul 23, 2026 ──▶ full list ──▶ StarMapper maps it
        │
        └── since Jul 23, 2026  ──▶ empty · 404, for everyone, every repo

What still works right now

These don't touch the stargazers list and never have.

Contributors MapWho codes a repo, mapped by location.Dependents ExplorerWho depends on a repo, and where they're based.Followers mapA GitHub user's followers, mapped.Trending reposRepos gaining stargazers fastest, from the pre-cutoff archive.Dev MapsExplore developers by language, country, and company.

Four ways forward

Stargazers list blocked (Jul 23, 2026)
        │
        ├──▶ [A] Engaged community pipeline ......... Already shipping
        ├──▶ [C] Contributors & dependents maps ...... Already live
        ├──▶ [D] Freeze pre-cutoff data as archive .... Already planned
        └──▶ [B] Owner-verified OAuth dashboard ....... Under evaluation

The four cards below are the ways StarMapper can move forward from here. Select any that apply, you can pick more than one, and submit when you're done.

A, C and D are already decided, voting there just tells me which to build first and gives me a number to point to. B is the real fork in the road: it is the only option that would add real login and start storing your GitHub token, something StarMapper has never done. "A plus C" is the answer most people land on, not an edge case.

Official sources

GitHub changelog (June 30 2026)Community discussion #202114 Community discussion #201209 Independent confirmation (daily-stars-explorer #363)