Microsoft’s GitHub Copilot is massive copyright infringement

Before you read this article – note that Codeium offers a competitor to GitHub Copilot. This means they have something to sell, and something to gain by making Copilot look bad. That being said – their findings are things we already kind of knew, and further illustrate that Copilot is quite possibly one of the largest, if not the largest, GPL violations in history.

To prove that GitHub Copilot trains on non permissive licenses, we just disable any post-generation filters and see what GPL code we can generate with minimal context.

We can very quickly generate the GPL license for a popular GPL-protected repo, such as ffmpeg, from a couple lines of a header comment.

Codeium claims it does not use GPL code for its training data, but the fact it uses code licensed more permissively still raises questions. While the BSD and MIT-like licenses are more permissive and lack copyleft, they still require the inclusion of the terms of the license and a copyright notice to be included whenever the covered code is used. I’m not entirely sure if using just permissively licensed code as training data is any better, since unless you’re adding the licensing terms and copyright notice with every autocompleted piece of code, you’re still violating the license.

If Microsoft or whoever else wants to train a coding “AI” or whatever, they should either be using code they own the copyright to, get explicit permission from the rightsholders for “AI” training use (difficult for code from larger projects), or properly comply with the terms of the licenses and automatically add the terms and copyright notices during autocomplete and/or properly apply copyleft to the newly generated code. Anything else is a massive copyright violation and a direct assault on open source.

Let me put it this way – the code to various versions of Windows has leaked numerous times. What if we train an “AI” on that leaked code and let everyone use it? Do you honestly think Microsoft would not sue you into the stone age?

26 Comments

  1. 2023-04-21 5:18 pm
    • 2023-04-21 9:57 pm
      • 2023-04-22 1:59 am
        • 2023-04-22 1:16 pm
          • 2023-04-22 2:38 pm
          • 2023-04-24 3:02 am
          • 2023-04-24 3:10 am
          • 2023-04-24 3:35 am
          • 2023-04-24 5:32 am
          • 2023-04-24 6:19 am
          • 2023-04-24 8:41 am
          • 2023-04-24 8:49 am
          • 2023-04-24 10:31 am
          • 2023-04-24 11:18 am
          • 2023-04-24 12:45 pm
          • 2023-04-24 5:57 pm
          • 2023-04-24 10:38 pm
          • 2023-04-25 2:58 am
          • 2023-04-25 10:54 am
      • 2023-04-24 10:51 am
        • 2023-04-24 11:38 am
          • 2023-04-24 12:21 pm
          • 2023-04-24 12:26 pm
          • 2023-04-24 10:45 pm
          • 2023-04-25 1:00 am
  2. 2023-04-23 5:08 pm