How US Sanctions Are Silencing GitHub Users Worldwide

The article examines how recent U.S. sanctions have led GitHub to restrict private repositories and access for developers in regions such as Crimea and Iran, detailing specific limitations, personal accounts affected, community workarounds, and the broader implications for open‑source collaboration.

21CTO
21CTO
21CTO
How US Sanctions Are Silencing GitHub Users Worldwide

GitHub is facing a supply‑chain crisis caused by U.S. sanctions, which now limit the ability of users in sanctioned regions to use private repositories and certain GitHub services.

One of the first reported cases involves Anatoliy Kashkin, a maintainer of the GameHub project living in Crimea. GitHub notified him that, due to U.S. trade‑control laws, his account is restricted: he can only access free public repositories, cannot create or maintain private ones, and existing private repos have been disabled.

Similar restrictions have affected Iranian developers. Hamed Saeedi, who has used GitHub since 2012, received an email stating his account was blocked under the claim that he was developing nuclear weapons. His personal GitHub Pages site returned a 404 error, and all private repositories were disabled, with git clone returning a 403 error.

GitHub Pages sites become inaccessible (404). Existing private repositories are disabled; cloning returns 403. Creating new private repositories is prohibited. Public repositories can be created but not deleted.

The restrictions also impact Iranian‑origin developers living abroad, such as an Iranian‑Finnish engineer, whose GitHub account was similarly limited despite residing in Finland.

Community members have suggested several workarounds: exporting data from private repos, migrating to GitLab (which currently offers unlimited private repositories), or using self‑hosted solutions like Gitea that are not based in the United States. However, access to GitLab may also be blocked in Crimea, and other platforms could eventually face similar sanctions.

Some developers have managed to rebuild their GitHub Pages sites after receiving a hint from a GitHub employee, but the employee has not answered questions regarding private repository access.

The overall advice emphasizes the importance of regularly backing up code and being prepared for sudden service restrictions caused by geopolitical factors.

Resources mentioned include the GitHub‑Do‑Not‑Ban‑Us repository, Hamed Saeedi’s Medium article, the GameHub issue discussing the restrictions, and the Hacker News discussion thread.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

information securityGitHubdata backupGeopoliticsaccount restrictions
21CTO
Written by

21CTO

21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.