Arguably, if your code is hosted by a third-party, the legal document is the least of your problems. If someone modified your legal documents without your knowledge, you are likely to be able to fight it as having been a victim of fraud yourself, and you wouldn&#x27;t be expected to abide by fraudulent contracts created by a third party impersonating you, right? (I don&#x27;t really know for sure, you are the attorney, but I&#x27;d be surprised if you were liable for forged contracts)<p>On the other hand, if your code is modified, it can exfiltrate data that you are never getting back, no matter what the legal system says. Even credit card numbers are not the worst, since in theory you can end up reversing every single fraudulent transaction made, and insurance might cover your liability. But in the case of Medium, it could, say, leak the real world identity of a blogger or citizen journalist in a place where doing so would put their lives at risk. So if you are already trusting a third party with the lives of your users who are trusting you with their lives (whether they should or not), is having the text of your EULA swapped by the lyrics of &quot;I am never gonna give you up&quot; really a worst case scenario?<p>At this point, given how many people use it as the authoritative source for their software, GitHub is already critical infrastructure, on par with GPS and the electrical grid of many countries. So if GitHub goes rogue or is compromised, the damage can be pretty catastrophic. Brave new world, ain&#x27;t it?