GitHub Has Restricted Access to Star Data
CompareStar Map How to use this site<br>On this page
GitHub Has Restricted Access to Star Data
Tianzhou·Jul 6, 2026<br>GitHub is restricting its stargazers API — the endpoint that returns who starred a repository and when. As announced on June 30, 2026, access to this data is being limited to a repository's own admins and collaborators .
Star History reconstructs a project's growth curve from exactly this data. So for any repository you don't own or collaborate on, an authenticated request to GitHub now returns "Not Found," and the chart can't be built.
Here is exactly what is and isn't impacted:
Impacted
Live star history charts embedded in README files — for essentially every repository, since our servers fetch the data and aren't a collaborator on your repo either.
Charts on star-history.com for repositories you don't own or collaborate on.
Not impacted
Viewing a repository you own or collaborate on, on star-history.com, with your own access token that can read it.
One caveat: tokens created with no scopes no longer work — even for your own repositories. See how to add your GitHub access token for the current setup.
What to do now
What to do depends on what you need:
Viewing star history for a repo you own or collaborate on. This still works — add an access token that can read it. Older no-scope tokens no longer work, so regenerate a fine-grained token.
Embedding a live chart for your own repo in a README. Supply a token that can read your repo — it's encrypted, so it's safe to put in a public README. See how to embed the chart in your README.
Charting a repo you don't own or collaborate on. GitHub no longer exposes this star data to anyone but the repo's admins and collaborators, so these charts are broken for now. We're still exploring workarounds and will share updates as we go.
Thank you for being a Star History user.
Subscribe
Bytebase- Database DevSecOps for Postgres, MySQL, Oracle, SQL Server, Mongo, Redis, and more.
Featured Products<br>Promote your product