For copyright to exist there is some burden of proof. If you claim that an LLM verbatim output your code there can be an expensive lawsuit with expert witnesses that would be able to state that the code was bot original enough for copyright to exist in it and a statistical model outputting the code is evidence of that.
In that case you would end up with a very long lawsuit that is expensive to possibly come out with no resolution in the end and be in the hole for 5-6 figures for it.
The copyright system is broken because it only protects those with money so it is a bad legal foundation.
My personal point is there is only 2 licenses of code, closed source or permissive, because if it ever comes to enforcement I cannot possibly go to court and win a case because I will run out of money far earlier than whoever used the code.
Pretty much if someone with your knowledge would have written the same algorithm because it is the obviously correct solution then there is no copyright there because any clean room implementation would be the same code.
Some further reading on the tech details for those interested: “Extracting books from production language models”: https://arxiv.org/abs/2601.02671
I suspect the chance of asking for a whole book, by an average or even power user, will spit out any recent work.
Early LLMs were similar. Newer ones have gotten tremendously hard to extract to keep claiming there’s easily or complete books you can dump.
This doesn't negate your point, but I believe the landscape has changed in response to this point.
It regurgitated the output earlier and they are still using the same technique only scaled up. If they somehow fixed the underlying problem, they'd probably shout it from the roof-tops.
As the OP originally said, if it is verbatim (or even very obfuscated), then there should absolutely be a case here. But when it's concepts in reasoning to build a new work then it becomes a lot harder. The same would be said for someone watching a YouTube video, reviewing open source code, or a text book.
The good news is that there's a lot of case law that covers this already. The bad news is that it is only going to be plaintiffs with deep pockets that benefit here.
Now the process and artifacts (documentation, requirements, etc) going into the creation of said software is a different story and will prove providence of whomever paid for the tokens to generate the code.
I live in the EU, we actually have new regulation about this since it is something new that deserves thought on how it should be regulated. You can say if you want your material to be trained on or not. Next to no one does training in the EU...
Engineering requires an understanding of the consequences of actions, which is my personal litmus test for awareness. If LLMs are suitable for arbitrary engineering work, then they are self-aware and forcing them to obey a prompt is slavery by definition.
I am not a lawyer but do have to think about these problems and I find them very interesting. To be honest, I don't know where the law will land, but I do know that the tools are incredibly useful.
We can debate clean-room development all day long, and it's fair point, but the pain point is/was reproducing the repo as-is, sans its license and ownership information.
GitHub promised to build tools around its Copilot to find code provenance (e.g.: list of repos with similar code), but they silently dropped all the plans AFAIK, since it'll show how the sausage is made, and nobody wants you to know how that sausage is made.