I got banned from GitHub for 2 weeks. Here’s what I learned about single-platform dependency

Description and use

The author built five independent download channels to mitigate the risk of GitHub bans and ensure continuous access to the code.

Problem

Relying solely on GitHub for code distribution exposed the project to sudden inaccessibility and hindered independent verification.

Outcome

By diversifying distribution channels, the project remained accessible even after a GitHub ban, enabling continuous verification and reducing single‑point failure risk.

Workflow

• 1. Host the source on GitHub and publish NPM packages.
• 2. Mirror NPM packages on jsDelivr and unpkg CDNs.
• 3. Deploy an origin server (marketnow.site) to host tarballs directly.
• 4. Create a public GitHub org (alicelabs-llc) for visibility.
• 5. Write an install script that queries each channel in order and uses the first successful download.

Evidence

55 public repos instantly returned HTTP 404 to anonymous visitors.

Source

All 5 channels serve byte‑identical tarballs (SHA‑256 verified).

Source

The installer script tries all 5 channels in order and uses the first one that works.

Source