Embed Notice

@lanodan I wouldn't probably support the code removal so directly. There is something to learn from the issue and it's not like there would not be vulnerable code on GitHub anyway (you can get e.g. Linux kernel v5.12-rc1-dontuse if you want). Imho the issue is not "someone could see the bad code", but "somebody could get it by mistake", at which point a better way would be ~making sure people can only download the code interactively and with seeing a big warning for some time.

But GitHub needs to be on good terms with their shareholders (not community), so it would make sense they would remove it preemptively. Also, if Jia got enough rights over the xz repo, they might have killed it themself, no GitHub employee involved.