Ask Lemmy

Yeah, but you also have to be aware that companies rarely care to (fully) comply with licenses to begin with, if their own code isn't publicly accessible.

Basically:

• If they actually open-source their own code, they have to fully comply (though the worst consequence is often just having to open-source your own code, which it already is, so it might not always be the highest priority either).
• If they build a frontend, they generally do want to comply, because someone might be able to decompile the software and prove that licensed code is used inappropriately.
• If they build a backend or build tooling or the like, GPL and AGPL is often still prohibited due to the high impact, but other than that, complying with licenses is seen as reducing risk for something that's pretty unlikely to affect them. The chance of them being sued for code that no one sees is just practically 0, so it's usually treated as an acceptable legal risk to not give a fuck.

Even before getting into the copyrightability of code, at the very least, any LLM-produced parts are not copyrightable. They are public domain.

That said, if its a mix of LLM code and human code, things get pretty messy. From my understanding, if the human expanded on or modified AI code, its public domain. If they wrote a section fully independently, they absolutely own the copyright. If its an unclear mix, it would have to be proven on a case-by-case basis with the onus being on the AI user to provide solid evidence that the code copied isn't AI generated.

Not if the code is not copyrightable, and it may not be