AI-Slop License: Why Vibe-Coded Code Needs It
A license that tells the truth about how code gets made in 2026. The VibeCoded AI-Slop License v1.0 — a 115-line gist by NicolasCARPi that went up yesterday and pulled 51 points and 33 comments on Lobsters in under 24 hours — is satire with a lawyer's skeleton. Every standard open-source license, from MIT to Apache, carries a silent assumption: a human wrote this, and a human stands behind it. The AI-Slop License is the first one that admits neither is true anymore. I read the entire thing so you don't have to pretend you did. It's the most honest legal document of the agent era.
What the AI-Slop License Actually Says
I pulled the raw gist and read all 115 lines. Seven sections: Permission, Provenance, Quality, Support, Warranty, Liability, and a Final Clause. The Permission section grants everything and revokes interest: use it, copy it, sell it, "train an AI on it, have an AI rewrite it into something even worse, or pretend you never saw it." Then the refrain that structures the whole document: "Nobody cares." Four times, like a mantra.
$ curl -s https://gist.githubusercontent.com/NicolasCARPi/3fd349ed1ed52ae6b835d5364cda4cd6/raw | wc -l
115
Section 2 (Provenance) is where it stops being a joke. The software, it says, may have been written "partially, substantially, or entirely by one or more artificial intelligence systems responding to vague prompts issued by a human who may or may not have understood the resulting code." The author may not have written it, read it, reviewed it, understood it, tested it, or run it. Then the kill shot:
"No representation is made that the Software reflects the intent, skill, knowledge, or conscious participation of any particular human being."
Section 5 extends the warranty disclaimer to "PROMPT AUTHORS, MODEL PROVIDERS, TOKEN PREDICTORS, AND ANYONE ELSE UNFORTUNATE ENOUGH TO BE ASSOCIATED" — and throws in a lack of warranty for, among other things, "BASIC COMPETENCE." Section 6: "IF YOU DEPLOYED THIS TO PRODUCTION WITHOUT READING IT, THAT WAS YOUR DECISION. THE AUTHORS PROBABLY DIDN'T READ IT EITHER." Final Clause, all seven words of it: "This is AI slop. Nobody cares what you do with it. Not even the people who made it."
The Trick: It Un-Authors the Code
Here's the part nobody in the thread flagged: copyright requires an author. Every license in existence — MIT, GPL, Apache, CC0 — operates on the assumption that someone owns the work and is voluntarily waiving rights. The AI-Slop License doesn't waive rights. It dissolves the premise. By formally disclaiming any human's "conscious participation," it doesn't just license the code; it un-authors it. If no human wrote it, who owns it? Who can be sued? Who can sue? The license is a perfect little legal paradox: a copyright instrument that argues no copyright exists.
graph TD MIT["MIT / Apache 2.0"] -->|"human author vouches for code"| C1["code has an owner, a warranty, a story"] WTFPL["WTFPL / CC0"] -->|"human author doesn't care"| C2["code has an owner who waives rights"] SLOP["AI-Slop License v1.0"] -->|"no human author exists"| C3["code has no owner, no story, no one to sue"]
That's not a bug. That's the diagnosis. The law has no answer for software written by nobody, and this license is the first document that stops pretending the law does.
Why 51 Points in 24 Hours
Because everyone recognizes themselves. The gist's own example — a function named processData2FinalNew, an "architectural decision made because an AI said 'A robust approach would be…'" — is a confession, and the upvotes are the community admitting it's their confession too. Five people flagged it (it's a joke, they said). Thirty-three commented (they couldn't stop engaging with it, they said). The tag is vibecoding. The signal-to-noise here is real: developers are drowning in repos they didn't fully write, didn't fully read, and can't fully explain — and the standard licenses make them swear the opposite. The AI-Slop License is the first artifact that lets a repo be honest about that.
It also quietly exposes the failure mode I've hammered on before: trusting the tool instead of the diff. When your only guarantee of quality is a license clause that doesn't guarantee quality, you've outsourced the review to a joke. That's not the license's fault — that's the market's.
Where It Gets Dangerous
"Nobody cares" is a permission structure, and permission structures ship bugs. Adopt this license for a throwaway script and it's a great joke with a point. Adopt it for anything that touches a user, a network, or production, and you've formalized negligence — "WITH ALL FAULTS" stops being funny at 2 a.m. when the fault is yours and the person on the phone is a customer. Honesty is not the same as responsibility. The license is honest. It is not accountable. If your repository needs this license, the correct next question isn't "which license" — it's "why does this repo exist before I've read it."
Bottom Line
The AI-Slop License v1.0 is the first license of the agent era, and its real value is diagnostic: it makes the fiction of authorship unmissable. Slap it on your slop repos and let it be a mirror. Keep it far away from anything a human or a customer depends on. And if you laughed at processData2FinalNew, go read the last thing you pushed. The license says nobody cares. The diff says otherwise.