GitHub took a 21TB snapshot of all active public repositories on February 2 and deposited it in the Arctic Code Vault on July 8 using 186 reels of archival film
At GitHub Universe 2019, we introduced the GitHub Archive Program along with the GitHub Arctic Code Vault.
Context & Ripple Effects
When GitHub introduced the Archive Program and the Arctic Code Vault at GitHub Universe 2019, the pitch was intent; this deposit makes it physical. A platform that already held over 100 million repositories and 31 million developers as of late 2018 has compressed every active public repository into a single 21TB snapshot and written it onto 186 reels of film.
The move matters because a film vault behaves differently from a data center: it is read-only, offline, and effectively immutable, so whatever was in those repositories on February 2 stays there exactly as it was.
First-order effects
- Every developer with an active public repository on February 2 now has a frozen copy of their code preserved independent of anything they do next — deletions, rewrites, and force-pushes after that date don't touch the archive.
Second-order effects
- An unpatchable archive collides with GitHub's own leak-remediation work: the secret-scanning alerts service and the push protection feature exist to stop API keys and tokens leaking from live repositories, but any credentials captured in the snapshot are permanently baked into the film.
Third-order effects
- If the vault is replenished on a recurring basis, GitHub's role shifts from hosting the working copy of open source to also being its designated long-term custodian — a registry position no competitor mirrors, since rivals would have to match both the storage commitment and the institutional continuity.
The trend: Code-hosting platforms are evolving beyond living repositories into keepers of permanent software archives, with periodic snapshot deposits turning GitHub's public corpus into a versioned historical record.