Large Proposal: Non-Standard Libraries

Alternatively, if you want your own repo that nobody can take down, create a fork.

That's a repo that you control, and the Swift project doesn't have to worry about hosting code which is malicious or potentially infringes on somebody's copyrights or patents. Sometimes code goes down for important reasons (even if it's a pain in the backside).