These aren&#x27;t new problems though; the same arguments apply if you replace &quot;repos&quot; with &quot;Web sites&quot; and &quot;GitHub&quot; with, say, &quot;GeoCities&quot; or &quot;Tumblr&quot;.<p>Package managers certainly aren&#x27;t tied to sites like GitHub; for example, I host my own Composer packages ( <a href="https:&#x2F;&#x2F;packagist.org&#x2F;users&#x2F;warbo&#x2F;" rel="nofollow">https:&#x2F;&#x2F;packagist.org&#x2F;users&#x2F;warbo&#x2F;</a> ). Unfortunately each package does tend to get tied to a particular Web address, but there are sporadic efforts to overcome this (e.g. <a href="https:&#x2F;&#x2F;wiki.debian.org&#x2F;DebTorrent" rel="nofollow">https:&#x2F;&#x2F;wiki.debian.org&#x2F;DebTorrent</a> )<p>If you consider GitHub to be a &quot;central place for FOSS code&quot;, which represents the unfragmented community, and serves as the only neccesary search engine and update notification system, then I regret to inform you that you&#x27;re mistaken. FOSS has been around far longer than GitHub, as has the Web. The community is incredibly fragmented, although pretty much all communicate via a combination of Websites, email, IRC and RSS feeds. GitHub has only ever been a rather recent fragment of this; although it would still be a great loss if all its projects were deleted overnight.<p>Like everything else on the Web, the current &quot;solutions&quot; are search and archiving on a massive scale. Perhaps P2P technologies like IPFS and magnet links will be (part of) a more scalable alternative going forward.