Good news!

[kroese]

Documentation Type

README

Current Documentation

Github published this article this week:

https://github.blog/changelog/2026-06-30-upcoming-access-restrictions-to-public-api-endpoints-and-ui-views/

What it boils down to is that it will remove access to the Stargazers API for repos that you do not own.

That means that all the other projects (Star History, Starchart.cc, etc) will stop functioning.

But your project is not affected, because it calls those API with the users own credentials.

So let's hope when people soon are forced to find an alternative, they discover this project!

Problem

...

Suggested Improvement

...

Example Use Cases

Target Audience

Beginners

References

No response

Contribution

• I'm willing to submit a PR to improve this documentation

[fbuireu]

Haha this made my day 😄 Thanks for the heads-up!

I saw the announcement and honestly my first thought was "well, there goes half the star-charting ecosystem". You're spot on about why this one dodges it: everything runs in your workflow, with your token, against your own repos, which is exactly the access GitHub is keeping. Star counts aren't even part of the restriction, and the stargazers list (what powers the charts and stargazer tracking) only needs admin/collaborator access, which you have by definition on your own repos.

I've added a notice to the README (#146) pointing people coming from Star History / Starchart.cc over here, so hopefully the refugees find their way 😅