Issue 605  April 14th 2023

I recently found this Copilot X plugin for Xcode from Shx Guo, and it set me thinking about my concerns about open-source licensing in AI-generated code again.

Before I get into it, I’ll clarify the problem. It relates to the implications of using code licensed under “copyleft” and GPL-style licenses in the training data for tools like CoPilot and other software based on OpenAI Codex. While successful prosecutions of GPL violations are rare, they are not unheard of, and the implications can be serious.

This case may set a precedent if it proceeds, but right now, nothing is clear. I’m not on one side of the argument or the other, honestly. I’m certainly not an advocate for copyleft licenses, but I respect that they exist and certainly care about the potential risks of using these tools.

I’d love to know how big companies like Apple are handling this risk. I can’t imagine any reality in which Apple has not prohibited these tools internally. Imagine if an Apple employee working on some code in iOS or macOS, and it happened to generate some amount of GPL-licensed code. No matter how slim the chance of that happening, or the even smaller chance of it being proven to create a derivative work, a company like Apple can’t risk being forced to open-source sections of their operating systems against their will. All of this is before I even consider how unhappy Apple would be at having any of their code transmitted to the tool as a prompt, but that’s not the main issue I’m talking about here.

You may read this as a solo developer or a small company and think this could never affect you. That you’re too small to be a target of this kind of litigation. You’re almost certainly correct, but imagine a few years from now, in the final stages of due diligence with a large company trying to acquire your app and the innocent question of “Was any of your code written with AI code generation?” comes up. 😳

I also have concerns over the vast amounts of unpaid and uncredited human effort being turned into yet more profit for huge companies, but again, to attempt to keep this short-ish, I won’t go into that here.

All that said, avoiding all new technology based on AI isn’t the correct choice either. The explosion of AI tools over the past year is only the beginning, and it will be really easy to be left behind. I’ve experimented with Midjourney quite a lot, and I pay for and use ChatGPT daily. I even used it as a starting point when researching this comment! Even with all of the problems with the early iterations of these tools, they are fascinating and already useful.

Should Apple be working to integrate tools like CoPilot into Xcode? Many people would be thrilled if they did, and I’m sure it’s not this licensing worry holding them back. If they don’t, how long will it be until Xcode is perceived to be falling behind, and how long before that affects the developer perception of Apple platforms? There are way more questions than answers here.

In all likelihood, it will be extremely challenging to prove the source of AI-generated snippets from such a large model, and that’s before you even get to the argument of whether code using those snippets could be a derivative work. GitHub CoPilot also has a feature to block generated suggestions that match public code, and while that’s a good feature it also feels like it acknowledges that there is a problem.

I’d just be much more comfortable experimenting with Codex-based tools if OpenAI had not used GPL-licensed training data.

Dave Verwer