You wake up one morning, reach for your phone, and open GitHub. Your profile is gone. Your repos — gone. The open-source project you’ve poured two years into — gone. No warning, no explanation. Just a 403 Forbidden page.
This isn’t hypothetical. It’s the quiet reality of life on a platform that answers to a government, not a community.
GitHub’s ‘No’ is the most political answer in tech. When the top comment on a Hacker News thread asks ‘Is GitHub politically influenced?’ and someone replies ‘No,’ they’re not wrong — they’re just missing the point. The real political influence doesn’t look like a left-right purge. It looks like a legal compliance officer in a Seattle office clicking a checkbox that cuts off a developer in Tehran.
Let me tell you a story. A few years ago, a developer in Crimea — a region under U.S. sanctions — found his GitHub account suspended. He hadn’t posted anything political. He hadn’t violated any code of conduct. He lived in a zip code that the U.S. Treasury Department had flagged. GitHub’s response? ‘We must comply with applicable sanctions.’ That’s it. No appeal. No human review. A machine in a cloud somewhere decided his code was illegal.
GitHub is an open platform for the world — until the world’s laws say otherwise. This is the tension nobody talks about: GitHub wants to be Switzerland for code, but it’s incorporated in California. And California answers to Washington. The moment a developer in a sanctioned country pushes a commit, the platform’s neutrality evaporates. It’s not a matter of ideology. It’s a matter of jurisdiction.
Think about what that means. Every developer in every country — from Belarus to Burma to Venezuela — is writing code on borrowed land. The servers are under U.S. control. The legal terms are U.S. law. The data is subject to U.S. subpoenas. You can build the most beautiful, apolitical, open-source project in the world, but if your IP address happens to fall inside a red line on a map, it’s gone.
The real political influence isn’t left vs. right — it’s national jurisdiction. And that’s scarier because it’s faceless. There’s no angry tweet, no mob, no culture war. There’s just a silent compliance system that treats your code as a liability, not a contribution.
I’ve seen this pattern before. In 2019, a developer from Iran lost access to his entire GitHub organization because of sanctions. He had been building tools for disaster response — earthquake mapping, medical supply chains. Zero politics. But GitHub’s terms of service said: ‘You may not use our products if you are located in a sanctioned country.’ So the earthquake mapper got locked out. The logic was legal, not political. The effect was devastatingly political.
This is the paradox of neutral infrastructure. Every platform that claims to be apolitical is actually deeply political — it’s just that its politics are hidden in the fine print. GitHub’s ‘No’ is a political answer because it accepts the premise that the question is about ideology, when it’s really about power. The question ‘Is GitHub politically motivated?’ assumes the motivation is a belief. The real answer is: the motivation is compliance. And compliance is a political choice — it’s the choice to enforce the laws of one country over the freedom of everyone else.
So what does this mean for you, the developer who thinks GitHub is just a tool? It means you’re building on a platform that can be weaponized against you — not because of what you believe, but because of where you were born. It means your open-source identity is only as stable as the legal relationship between your country and the United States. It means the next time you see a ‘No’ on a thread about political influence, you should ask: ‘Whose politics are being served by that answer?’
The most dangerous political speech is the one that insists it isn’t political. GitHub’s ‘No’ is a perfect example. It’s technically correct — GitHub doesn’t delete accounts based on political views. It deletes them based on legality. But legality is just politics with a different uniform. The question isn’t whether GitHub is political. It’s whether we’re willing to admit that our digital commons is a fiefdom of a single nation-state.
I’m not saying GitHub is evil. I’m saying it’s honest enough to follow the law. But the law is not neutral. And neither is the platform. The only way to fix this is to build infrastructure that doesn’t depend on the goodwill of a single government — decentralized, jurisdiction-agnostic, truly global. Until then, every commit you push is a lease, not a deed.
So the next time you see a developer from a sanctioned country post a ‘Help, my account is gone’ thread, remember: that could be you. Not because of what you said. Because of where you are. And that’s the most political thing of all.
FAQ
Q: Does GitHub actually delete accounts just because of someone's location?
A: Yes, if that location is under U.S. sanctions. GitHub is required to comply with the Office of Foreign Assets Control (OFAC). Developers in Iran, Syria, North Korea, Crimea, and other sanctioned regions have had accounts suspended without warning. It's not about ideology — it's about jurisdiction.
Q: What should I do if I'm a developer relying on GitHub for critical projects?
A: Diversify your infrastructure. Mirror your repos to a self-hosted Git server or a decentralized platform like Radicle or SourceHut. Don't put all your code in one jurisdiction. If you're in a safe country, consider that the political climate can shift faster than you think. And if you're in a sanctioned region, use a VPN and a non-U.S. account service — but understand the risks.
Q: Isn't this just a fringe issue for a few countries? Why should most developers care?
A: Because the precedent is dangerous. Today it's Iran and Syria. Tomorrow it could be any country that falls out of favor with the U.S. — or any country that imposes its own sanctions. If GitHub becomes the standard for code hosting globally, then every developer is at the mercy of U.S. foreign policy. The platform's neutrality is a myth, and myths turn into traps when you least expect them.