1<!DOCTYPE html> 2<html> 3<head> 4<meta charset="UTF-8"/> 5 6<meta name="viewport" content="width=device-width, initial-scale=1"/> 7<meta content="GitHub Copilot litigation · Joseph Saveri Law Firm & Matthew Butterick" name="title"/><meta content="GitHub Copilot litigation" name="description"/><meta content="website" property="og:type"/><meta content="https://githubcopilotlitigation.com/" property="og:url"/><meta content="GitHub Copilot litigation · Joseph Saveri Law Firm & Matthew Butterick" property="og:title"/><meta content="GitHub Copilot litigation" property="og:description"/><meta content="https://githubcopilotlitigation.com/img/og-image.png?1744395456" property="og:image"/><meta content="summary_large_image" property="twitter:card"/><meta content="https://githubcopilotlitigation.com/" property="twitter:url"/><meta content="@mbutterick" property="twitter:sitel"/><meta content="GitHub Copilot litigation · Joseph Saveri Law Firm & Matthew Butterick" property="twitter:title"/><meta content="GitHub Copilot litigation" property="twitter:description"/><meta content="https://githubcopilotlitigation.com/img/og-image.png?1744395456" property="twitter:image"/>
8<script async src="//static.getclicky.com/101386305.js"></script>
8 9<link rel="stylesheet" type="text/css" media="all" href="styles.css" /> 10<title>GitHub Copilot litigation · Joseph Saveri Law Firm & Matthew Butterick</title> 11</head> 12<body> 13 14<main><nav class="topnav"><div hyphens="none"><a href="/">GitHub Copilot litigation</a></div><div hyphens="none"><a href="case-updates.html">case updates</a></div><div hyphens="none"><a href="//www.saverilawfirm.com/our-cases/github-copilot-intellectual-property-litigation">get updates by email</a></div><div hyphens="none"><a href="#contacting-us">contact legal team</a></div></nav><h1 link="false">Weâve filed a lawÂsuit chalÂlengÂing GitHub CopiÂlot, an AI prodÂuct that relies on unpreceÂdented open-source softÂware piracy.<br/><strong>Because AI needs to be fair & ethÂiÂcal for everyÂone.</strong></h1><p class="datestrip" id="22-11-03"><a href="#22-11-03" style="color: inherit">NovemÂber 3, 2022</a></p><p>Hello. This is <a href="//matthewbutterick.com">Matthew Butterick</a>. On OctoÂber 17 <a href="//githubcopilotinvestigation.com">I told you</a> that I had teamed up with the <a href="https://www.saverilawfirm.com/our-cases/">amazÂingly excelÂlent</a> class-action litÂiÂgaÂtors <a href="//www.saverilawfirm.com/attorneys/joseph-r-saveri/">Joseph Saveri</a>, <a href="//www.saverilawfirm.com/attorneys/cadio-zirpoli">Cadio ZirÂpoli</a>, and <a href="//www.saverilawfirm.com/attorneys/travis-manfredi">Travis ManÂfredi</a> at the <a href="//www.saverilawfirm.com/our-cases/github-copilot-intellectual-property-investigation">Joseph Saveri Law Firm</a> to invesÂtiÂgate GitHub CopiÂlot.</p><p>Today, weâve filed a class-action lawÂsuit in <a href="//www.cand.uscourts.gov/">US fedÂeral court</a> in San FranÂcisco, CA on behalf of a proÂposed class of posÂsiÂbly milÂlions of GitHub users. We are chalÂlengÂing the legalÂity of <a href="//github.com/features/copilot">GitHub CopiÂlot</a> (and a related prodÂuct, <a href="//openai.com/blog/openai-codex/">OpenAI Codex</a>, which powÂers CopiÂlot). The suit has been filed against a set of defenÂdants that includes <a href="//github.com/about">GitHub</a>, <a href="//www.microsoft.com/en-us/about">Microsoft</a> (owner of GitHub), and <a href="//openai.com/">OpenAI</a>.</p><p>Todayâs filÂings:</p><ul><li><p><a href="pdf/06823/1-0-github_complaint.pdf">Class-action comÂplaint</a></p></li><li><p><a href="pdf/06823/1-1-github_complaint_appendix_a.pdf">Class-action comÂplaint: AppenÂdix A</a></p></li><li><p><a href="pdf/06823/1-2-github_complaint_exhibit_1.pdf">Class-action comÂplaint: Exhibit 1</a></p></li></ul><p>By trainÂing their AI sysÂtems on pubÂlic GitHub reposÂiÂtoÂries (though based on their pubÂlic stateÂments, posÂsiÂbly much more) we conÂtend that the defenÂdants have vioÂlated the legal rights of a vast numÂber of creÂators who posted code or other work under cerÂtain open-source licenses on GitHub. Which licenses? A set of 11 popÂuÂlar open-source licenses that all require attriÂbuÂtion of the authorâs name and copyÂright, includÂing the <a href="https://opensource.org/licenses/MIT">MIT license</a>, the <a href="https://opensource.org/licenses/GPL-3.0">GPL</a>, and the <a href="https://opensource.org/licenses/Apache-2.0">Apache license</a>. (These are enuÂmerÂated in the <a href="pdf/06823/1-1-github_complaint_appendix_a.pdf">appenÂdix to the comÂplaint</a>.)</p><p>In addiÂtion to vioÂlatÂing the attriÂbuÂtion requireÂments of these licenses, we conÂtend that the defenÂdants have vioÂlated:</p><ul><li><p>GitHubâs own <a href="https://docs.github.com/en/site-policy/github-terms/github-terms-of-service">terms of serÂvice</a> and <a href="https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement">priÂvacy poliÂcies</a>;</p></li><li><p><a href="https://www.law.cornell.edu/uscode/text/17/1202">DMCA § 1202</a>, which forÂbids the removal of copyÂright-manÂageÂment inforÂmaÂtion;</p></li><li><p>the <a href="https://oag.ca.gov/privacy/ccpa">CalÂiÂforÂnia ConÂsumer PriÂvacy Act</a>;</p></li><li><p>and other laws givÂing rise to related legal claims.</p></li></ul><p>In the weeks ahead, we will likely amend this comÂplaint to add other parÂties and claims.</p><p>This is the first step in what will be a long jourÂney. As far as we know, this is the first class-action case in the US chalÂlengÂing the trainÂing and outÂput of AI sysÂtems. It will not be the last. AI sysÂtems are not exempt from the law. Those who creÂate and operÂate these sysÂtems must remain accountÂable. If comÂpaÂnies like Microsoft, GitHub, and OpenAI choose to disÂreÂgard the law, they should not expect that we the pubÂlic will sit still. AI needs to be fair & ethÂiÂcal for everyÂone. If itâs not, then it can never achieve its vaunted aims of eleÂvatÂing humanÂity. It will just become another way for the privÂiÂleged few to profit from the work of the many.</p><p>We plan to update this webÂsite regÂuÂlarly durÂing the litÂiÂgaÂtion. Please join <a href="//www.saverilawfirm.com/our-cases/github-copilot-intellectual-property-litigation">our email list</a> for the latÂest.</p><p class="datestrip" id="22-11-10"><a href="#22-11-10" style="color: inherit">NovemÂber 10, 2022</a></p><p>Weâve filed a secÂond class-action lawÂsuit in <a href="//www.cand.uscourts.gov/">US fedÂeral court</a> in San FranÂcisco, CA on behalf of two addiÂtional plainÂtiffs. The defenÂdants and claims are othÂerÂwise simÂiÂlar to the iniÂtial comÂplaint filed on NovemÂber 3.</p><p>Todayâs filÂings:</p><ul><li><p><a href="pdf/07074/1-0-github_complaint.pdf">Class-action comÂplaint</a></p></li><li><p><a href="pdf/07074/1-1-github_complaint_appendix_a.pdf">Class-action comÂplaint: AppenÂdix A</a></p></li><li><p><a href="pdf/07074/1-2-github_complaint_exhibit_1.pdf">Class-action comÂplaint: Exhibit 1</a></p></li></ul><h2 id="contacting-us"><a href="#contacting-us">ConÂtactÂing us</a></h2><p>If youâre a memÂber of the press or the pubÂlic with other quesÂtions about this case or related topÂics, conÂtact <a href="mailto:[email protected]">github_inquiries@saverÂiÂlawÂfirm.com</a>. (Though please donât send conÂfiÂdenÂtial or privÂiÂleged inforÂmaÂtion.) More inforÂmaÂtion about the backÂground of this case is <a href="//githubcopilotinvestigation.com/">availÂable here</a>.</p><div class="warningbox"><div class="inner">This web page is inforÂmaÂtional. GenÂeral prinÂciÂples of law are disÂcussed. But neiÂther Matthew Butterick nor anyÂone at the Joseph Saveri Law Firm is <em>your</em> lawÂyer, and <strong>nothÂing here is offered as legal advice</strong>. RefÂerÂences to copyÂright perÂtain to US law. This page will be updated as new inforÂmaÂtion becomes availÂable.</div></div><div style="padding-top:2rem"> </div></main> 15</body> 16</html> 17<!-- 18© 2025 The Joseph Saveri Law Firm and Matthew Butterick 19made with Pollen (pollenpub.com) 20built Friday, April 11th, 2025 11:17:36am 21-->
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.