This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Star History Revived
The classic GitHub star history chart, rebuilt and revived
A drop-in fork and revival of the original star-history tool. It fixes the dead SVG charts across thousands of GitHub READMEs caused by GitHub's API deprecations, delivering instant star tracking without requiring personal access tokens
If you maintain or use open-source projects with star-growth charts in their README.md, you may have noticed that many recently broke or died. This was caused by GitHub. Because they think that people were using the API too much, they removed it. They even broke their own UI because they forgot to update the frontend.
Unfortunately, this is killing the original star-history project. Since I relied on it, I looked for solutions but there were only two:
- Give away a token with complete write access on my repositories to random guys on the internet so that they can generate the chart for me - Build a complex pipeline to regenerate it frequently, handle maintenance and manage the token myself
The second option requires too much effort, so most people will prefer the first. It's a shame that Github didn't think about this and didn't measure the risks it implied. Now, there will be thousands of tokens with write access to the biggest repositories in the world, concentrated on a single third-party server. I'm not saying they can't be trusted, but everyone can and will get hacked eventually, so we shouldn't have to do this in 2026.
However I was lucky to have a third option. I happened to have snapshots of the necessary data for almost all repositories above 200 stars, thanks to another Github-related project. This allowed me to just fork the original project and make it use my own data instead, which I just need to keep updated frequently using public stargazer counts.
This results in a maintained drop-in replacement that does NOT require authentication or tokens. If you already use star-history in your README, you can keep it working exactly the way it was. Just swap the domain to https://star-history.dera.page.
Would love to hear your feedback!
About Star History Revived on Product Hunt
“The classic GitHub star history chart, rebuilt and revived”
Star History Revived was submitted on Product Hunt and earned 5 upvotes and 1 comments, placing #94 on the daily leaderboard. A drop-in fork and revival of the original star-history tool. It fixes the dead SVG charts across thousands of GitHub READMEs caused by GitHub's API deprecations, delivering instant star tracking without requiring personal access tokens
On the analytics side, Star History Revived competes within Open Source and GitHub — topics that collectively have 110.1k followers on Product Hunt. The dashboard above tracks how Star History Revived performed against the three products that launched closest to it on the same day.
Who hunted Star History Revived?
Star History Revived was hunted by Mubelotix. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Star History Revived including community comment highlights and product details, visit the product overview.
Mubelotix
Hey Product Hunt! 👋
If you maintain or use open-source projects with star-growth charts in their README.md, you may have noticed that many recently broke or died. This was caused by GitHub. Because they think that people were using the API too much, they removed it. They even broke their own UI because they forgot to update the frontend.
Unfortunately, this is killing the original star-history project. Since I relied on it, I looked for solutions but there were only two:
- Give away a token with complete write access on my repositories to random guys on the internet so that they can generate the chart for me
- Build a complex pipeline to regenerate it frequently, handle maintenance and manage the token myself
The second option requires too much effort, so most people will prefer the first. It's a shame that Github didn't think about this and didn't measure the risks it implied. Now, there will be thousands of tokens with write access to the biggest repositories in the world, concentrated on a single third-party server. I'm not saying they can't be trusted, but everyone can and will get hacked eventually, so we shouldn't have to do this in 2026.
However I was lucky to have a third option. I happened to have snapshots of the necessary data for almost all repositories above 200 stars, thanks to another Github-related project. This allowed me to just fork the original project and make it use my own data instead, which I just need to keep updated frequently using public stargazer counts.
This results in a maintained drop-in replacement that does NOT require authentication or tokens. If you already use star-history in your README, you can keep it working exactly the way it was. Just swap the domain to https://star-history.dera.page.
Would love to hear your feedback!