From time to time, I check that our open-source project is still available to all users, and I've occasionally noticed that the stargazers (1) information returns a 404 for non-logged-in users.
I assume they're preparing to follow the LinkedIn model by making access available to registered users only.
Have you noticed that GitHub has started blocking access to certain functions/pages for users without an account?
1. https://github.com/tirrenotechnologies/tirreno/stargazers
I think it’s been functionally login-only for a while, unfortunately.
Any time I try to use the site while logged out I immediately hit all sorts of rate limits and spam prevention measures. Issues and pull requests stop loading almost immediately. Searches are extremely restricted, like i think literally one search is all you get sometimes unless you login.
It’s hard to tell how much of this is intentional and how much is GitHub infra not being stable. My daily renovate bot that looks for updates for specific packages times out and encounters errors almost every time it runs and it’s barely doing anything. And it has an api key. I know I’m not hitting limits, some queries just don’t work >50% of the time on some repos.
Sometimes I see there are 200 issues, I click the issues tab, and there are zero. Is GitHub down? Am I rate limited? Do I just need to login? Or I know an issue/PR exists, and it just doesn’t appear when I search for the title or keywords verbatim. I just manually bookmark or subscribe to any important issue or PR now because the UI can’t be trusted anymore.
Fine for my closed source stuff, but my open source work is specifically meant to be viewable, even by non-technical people doing recruitment or looking over my portfolio.
I've put up with a lot of stuff, but this would be my personal last straw.
The whole GitHub infra is cracking under the AI-boom's increased load. This can very well be just another symptom of the same thing.
I think this would push even more small to medium sized busineses towards self hosting which I would love to see
It basically already is. You can’t use the search logged out and my agent can’t fetch issue comments.
Some parts of the website are explicitly login-only, yes. I sometimes tend to follow link to gh from my mail on phone where I'm not logged in and found that e.g. you can't see any CI results without logging in.
With AI and all the new projects/forks/updates, github is one busy place.
I wasn't browsing /trending on github until I started using AI, wanting to see what cool projects people are working on.
Advanced Search doesn't work unless you're logged in, but it's been like that for at least a year.
I can't even access that link with an account.
Hard to say, the only people who know are those internal to MS and GH and know, or who have told others. You have copies of your repos in other systems, yeah? Have a plan you don't need rather than need a plan you don't have.
Ask HN: What alternatives to GitHub are you using? - https://news.ycombinator.com/item?id=44876289 - August 2025 (97 comments)
I believe so. I cannot view any repository from my phone. It asks me to log in first.
Looking at how much work GitLab has to do due to abuse of being open, I don't blame anyone for wanting to make that change.
GitHub specifically put out a changelog about the stargazers API endpoint to restrict open access because of its use for spam and abuse. I believe this is more about user data than code. Obviously restricting public access to Git would be a different tier.
that is github.com you are referring to, would pulling public repos the curl -fsSL way need to be authenticated?
AI ruined everything. They have to protect "their" code.
Just to nitpick, requiring a free account is substantially different from a paywall.
I don't have an immediate direct source but read yesterday GitHub stars are being "obfuscated" because they're being scraped to spam popular projects -- or something similar.
Edit found the link [0], do not believe it mentions reason but links github blog
From Github [1]: > These endpoints and views currently expose public lists of stargazers and watchers, and this information has increasingly been misused to collect user data for spam activities which negatively impacts user experience and platform trust.
[0]: https://www.star-history.com/blog/github-stargazer-api-restr...
[1] https://github.blog/changelog/2026-06-30-upcoming-access-res...