They Said an AI Built It. Turns Out It Cloned an Open-Source Project. Welcome to 'Copyright Laundering'

“I built it over a weekend, just told the AI what I wanted.” You hear some version of this constantly now. But what if the “weekend build” was actually someone else’s open-source project, lifted almost wholesale? A controversy bubbling up in developer circles this past month lands squarely on that question.

A quick note: this case is recent enough that there isn’t a deep pool of public discussion to cite hard numbers from. So instead of leaning on specifics, this piece focuses on the structural questions the episode raises. They’re the part that outlasts any single dispute.

The Setup: A Data Room “Built With Vibe Coding”

The story is simple. Someone shipped a data room product. If that term is new to you: a data room is a secure online space where a company shares sensitive documents with investors or deal partners. During an acquisition or a fundraise, you can’t just email financials and contracts to whoever asks. So companies use a dedicated platform that controls access permissions and logs who viewed what.

The builder marketed this one as “made with vibe coding.” Vibe coding, for the uninitiated, is the term that blew up over the past year. Instead of writing code line by line, you tell an AI “build me an app that feels like this” in plain language and ride the vibe. It’s become the symbol of a moment: the promise that anyone who can prompt an AI can ship a product, no engineering background required.

Then the accusations started. The data room looked suspiciously close to an existing open-source project called Papermark.

What Papermark Actually Is

Papermark is a well-known open-source data room service, often described as the open-source alternative to DocSend. DocSend is the commercial document-sharing-and-tracking tool you’ve probably heard of; Papermark took that feature set and made it free to use, with the code open for anyone to inspect.

Here’s the part people get wrong. Open source does not mean “take it and do whatever you want.” Most open-source projects ship with a license. Attribute the source. Publish your modifications under the same terms. Negotiate separately for commercial use. The Papermark dispute comes down to exactly this: were the license terms honored, and was the source credited?

Copying someone’s code isn’t really the crime here. The crime is dressing that code up as something you built fresh with AI.

The Gray Zone Vibe Coding Created: ‘Copyright Laundering’

This is where it gets interesting. In the old days, copying code got caught fast. Variable names, comments, file structure — they all came along for the ride. Push an identical file to GitHub and a diff would expose it in seconds.

AI changed the math. Feed open-source code into a model and say “rewrite this” or “restructure it,” and what comes out looks nothing like the original. Same functionality, but the variable names are different, the file layout is different, the comments are gone. Put it side by side with the source and you can’t point and say “that’s a copy.”

The community has a name for this: copyright laundering. Like money laundering, one spin through the AI washing machine and the origin gets blurry. “An AI made it” starts working like a get-out-of-jail-free card — even when the underlying code carries someone else’s labor and someone else’s license.

Why This Isn’t Just Gossip

There are real reasons this shouldn’t be filed under petty drama.

First, trust in the open-source ecosystem. Developers release code for free out of goodwill — the idea is “let’s build on this together.” If that code keeps getting reborn as someone’s commercial product, no attribution, license ignored, why would anyone keep publishing?

Second, the credibility of “built with AI.” Vibe coding only has value if the premise holds — that the AI actually produced something new. The moment that label becomes wrapping paper for plagiarism, the honest builders get tarred too. Everyone who genuinely shipped something with AI now has to prove they didn’t just launder a repo.

Third, the accountability fog. A new excuse becomes available: “The AI trained on that code and wrote something similar — I didn’t copy anything.” Plagiarism by a person and plagiarism with an AI accomplice are not the same thing, and we haven’t drawn the line between them yet.

The Question Worth Sitting With

Technology always outruns ethics. Vibe coding is a genuinely great lever for lowering the barrier to building — and it’s also blurring an old question in a new way: who actually made this?

In the end it comes down to posture, not tooling. If you built something with AI, say where the ingredients came from. If you used open source, honor the license and credit the source. It sounds almost too obvious to state. But in an era when the AI washing machine runs nonstop, the obvious is getting harder to see. Next time you look at a product that was “built with AI,” will you stop to ask whose code is actually inside it?