Comment by nineteen999

> Courts don't work by saying, "oh, but everyone is doing it! Not much we can do now."

No, but they do recognise when their case registrations are filling up in a way that they cannot possibly process and make adjustments. Courts do not have an infinite capacity.

There's a really simple solution that you may not have considered:

1) don't put your vibe-coded source code in a public git repo, keep it in a local one, with y'know, authentication in front of it;

2) regularly ask your agents to review the code for potential copyright infringements if you either want to release the source or compiled code to the public at any point.

As long as you've followed best practices, I can't see why this is really going to become an issue. Most copyright infringements need to start with Cease & Desist anyway or they'll be thrown out of court. The alleged offender has to be given the opportunity to make good.

So "Claude, we received a C&D for this section of code you stole from https://.../ , you need to make a unique implementation that does not breach their copyright".

You will be surprised how easily this can be resolved.