GitHub Has Restricted Access to Star Data

Lobsters Hottest News

Summary

GitHub has restricted access to its stargazers API, limiting star data to repository admins and collaborators, breaking many star history charts.

<p><a href="https://lobste.rs/s/isvjz0/github_has_restricted_access_star_data">Comments</a></p>
Original Article
View Cached Full Text

Cached at: 07/07/26, 04:18 PM

# GitHub Has Restricted Access to Star Data Source: [https://www.star-history.com/blog/github-stargazer-api-restriction/](https://www.star-history.com/blog/github-stargazer-api-restriction/) GitHub is restricting its**stargazers API**— the endpoint that returns who starred a repository and when\. As[announced on June 30, 2026](https://github.blog/changelog/2026-06-30-upcoming-access-restrictions-to-public-api-endpoints-and-ui-views/), 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](https://www.star-history.com/blog/how-to-use-github-star-history#how-to-add-your-github-access-token)for the current setup\. ## What to do now What to do depends on what you need: 1. **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](https://www.star-history.com/blog/how-to-use-github-star-history#how-to-add-your-github-access-token)\. 2. **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](https://www.star-history.com/blog/how-to-use-github-star-history#how-to-embed-the-chart-in-your-readme)\. 3. **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\.

Similar Articles

Incident with Github.com

Hacker News Top

GitHub is experiencing high error rates and degraded performance across multiple services, including web, API, Git Operations, Webhooks, and Copilot, with ongoing investigations and mitigations.

GitHub Is Experiencing Difficulties

Hacker News Top

GitHub is experiencing a major outage affecting multiple services including GitHub Actions, Pages, Copilot, and Enterprise Importer, with workflow failures and delays. Engineers are actively working on mitigations.

Changes to GitHub Copilot individual plans

Hacker News Top

GitHub pauses new Copilot Individual sign-ups and tightens usage limits while removing Opus models from Pro tier to curb soaring compute demand from agentic workflows.