💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

The stargazers page was useful when I wanted to check whether a repo might have fake stars. It's not 100% accurate, but if I noticed several stargazers had also starred the same set of repositories, it was a strong signal that something was suspicious. Unfortunately, that's no longer possible.

Ii created gitranc.com to be able to compare repositories for myself and now i am also affected by this. At least give pro users the ability to do the same thing on the domain github.com.

Let's hope GitHub sees this thread and perhaps comes up with some compromise solution. Tracking stars over time is a pretty big use case, most of the tooling doesn't care about the user names. Though for those looking into the credibility of the project that does help.

I strongly oppose this change.

The /stargazers page served far beyond analytics or checking whether stars were legitimate. It played a key role in GitHub’s social and discovery layer.

For small and niche repositories, the list of stargazers was often one of the best ways to discover people working with similar technologies, find related projects through their profiles, understand what kind of community was forming around a repository, and connect with developers who shared the same interests. Many small projects have few issues, pull requests, forks, or discussions, so their stargazer list may be the only visible signal of the people interested in them.

Removing the entire public page because some actors abused it is a disproportionate response. GitHub could address scraping and spam through authentication requirements, stricter rate limits, pagination limits, abuse detection, partial visibility, anonymized historical data, or privacy controls for individual users. Blocking all legitimate access should not be the default solution.

This change turns stars from a public expression of interest into an opaque counter. That weakens project discovery, community formation, ecosystem research, and trust assessment across open source.

Please restore the public stargazers page, even in a limited form, or provide a replacement that preserves both star history and the ability to discover the community around a project.

Time to fork github and host our open source projects elsewhere.

In all seriousness not happy about this either

Literally leaving github.
Furthermore, "You Know" tab means nothing. Only letting the repo owner know does not have any positive effect to us, yet making everything a black box.

Btw, earlier this day, github has sneakily added the stargazer restriction to GraphQL as described in emanuelef/daily-stars-explorer#363.

resending this message i said from another related topic: i feel like visibility to /stargazers on public repositories should at least be limited to users with a minimum age honestly...