Asahi Linux Went GPL. AI Made MIT Too Easy to Launder.
Asahi Linux is going GPL after its code was rewritten with LLMs to hide where it came from. MIT was built for a world where copying still took effort.
The best Linux-on-Mac project in the world just decided MIT was a mistake.
On November 7, Asahi Linux used its Linux 7.3 progress report to announce something bigger than a kernel bump. Asahi Linux is going GPL. Every repository moves from MIT to GPLv2-or-later, and from now on the project says it will only ship strong copyleft code.
The reason is the part worth paying attention to.
Asahi says people pulled in-development code straight out of contributors' personal forks. Some of it got published without credit. Some of it got rewritten with LLM assistance to hide where it came from.
That's not a licensing dispute. That's a new kind of copying, and it's going to hit a lot more projects than this one.
What Asahi Linux Actually Changed With the GPL Move
Asahi has spent five years reverse-engineering Apple Silicon so the rest of us can run Linux on M-series Macs. GPU drivers. The m1n1 bootloader. Power management. Some of the hardest low-level work happening in open source right now.
Most of it was MIT-licensed. That meant anyone could take it, close it, sell it, and owe nothing except a copyright notice.
The 7.3 report says the team became aware of "multiple attempts" to use that freedom to replace the project and, in their words, aggressively monetise Linux on Apple Silicon.
Then came the line that got quoted everywhere:
"The MIT licence explicitly allows this, and has no carveouts to protect against bad faith actors."
They also pointed at history. WINE started out permissive too. Companies built proprietary forks on top of it and sold them. In 2002, WINE moved to the LGPL to push those companies back upstream.
Asahi's summary of that lesson: "Those who do not learn from history are doomed to repeat it."
A few things the announcement did not do, because they matter:
- It didn't name anyone.
- It said the team will "begin the process," so this isn't finished.
- It didn't explain how every past contributor signed off on the relicense.
The Omarchy Backdrop Everyone Is Reading Into
The timing is hard to ignore.
On November 4, three days before the report, DHH's Omarchy shipped version 4.5 with Mac support built on top of Asahi's work. DHH responded publicly after the announcement, saying Asahi had turned down upstreaming and that Omarchy had extended the work rather than taken it.
Asahi never named Omarchy. Other forks have popped up this year too, including AI-assisted driver work maintained outside the main tree.
I'm not going to pretend I know who did what. Neither does anyone posting hot takes on X.
But you don't need a villain for the core point to land. Asahi is a small team doing years of painful work, and it watched people walk off with that work faster than the license could keep up.
The License Laundering Problem Is New
Here's what changed, and it's not the license text.
MIT has exactly one real obligation: keep the copyright and permission notice. That's it. The whole social contract of permissive open source rests on that notice surviving.
For thirty years, that held up. Copying code by hand left fingerprints. Same variable names. Same comments. Same weird workaround for the same weird hardware bug. If you stripped the notice, someone could usually prove you'd copied.
Now you paste a driver into a model and say "rewrite this in a different style." Ten minutes later you have something that does the same thing, looks different, and carries no notice at all.
That's license laundering. The code's ideas and hard-won reverse-engineering findings survive. The attribution doesn't.
I do this kind of transformation all day. I use Claude Code to port patterns between my own repos constantly. Renaming, restructuring, translating a Python helper into TypeScript. It's the most normal thing in my workflow.
Point that same workflow at someone else's MIT repo, strip the origin, and ship it as yours. Mechanically it's the same task. Ethically it's theft with extra steps.
I wrote about AI slop pull requests draining maintainer time earlier this year. This is the other half of that problem. AI doesn't just flood maintainers with bad contributions. It also makes it cheap to take their good ones.
Why GPL Won't Fully Stop It Either
The critics have real points, and I want to be fair to them.
Stripping an MIT notice is already a violation. If someone took unpublished code from a personal fork, that's plain infringement under any license. GPL doesn't add a new crime there.
OpenBSD developer Bryan Steele called the move "burning bridges for no reason." OpenBSD's Apple Silicon support leans on Asahi's m1n1, so that's not an abstract complaint. A permissive downstream just lost a permissive upstream.
There's the consent question too. Several people, including Jeff Geerling in the LWN comments, raised whether you can relicense contributors' MIT code without asking each of them.
And a determined bad actor who launders code through an LLM doesn't care what the license says. They're already ignoring the one rule MIT had.
So what does GPL actually buy Asahi?
It changes the default for everyone acting in good faith. A company that wants to build a commercial Mac Linux distro on Asahi now has to publish its changes. The cheapest legal path stops being "fork and close" and becomes "contribute back."
That's not a lock. It's a fence. Fences still work on most people.
The Uncomfortable Take
Most builders I know pick MIT without thinking. I've published to npm. I've never spent more than a minute choosing a license.
We pick MIT because it's friendly. Because companies won't touch GPL. Because we want stars and adoption more than control.
Here's the part nobody wants to say out loud: MIT has been quietly subsidizing the indie SaaS boom, and AI just raised the size of the subsidy.
Every "I built this in a weekend" launch, including some of mine, runs on permissive code someone else wrote for free. That was always true. What's new is how little effort it now takes to absorb someone's work so completely that the original author disappears from it.
If you're shipping fast with AI, you are the person these licenses are now being written against. Not because you're malicious. Because your tooling makes laundering the path of least resistance, and you probably haven't noticed.
I'd bet Asahi is the first well-known project of many to make this switch. Others will do it quietly. Some will go further, toward source-available licenses that restrict commercial use and AI training outright.
The builders complaining loudest about that shift will mostly be the ones who benefited most from the old deal.
What I'm Changing in My Own Stack
Two concrete things.
First, I'm actually checking what I depend on. Most of us have no idea what licenses sit in our dependency tree, and relicenses like this one only affect new versions, which is exactly when you stop paying attention.
# Summarize every license in your production dependencies
npx license-checker --production --summary
# Flag anything copyleft before it surprises you in a client project
npx license-checker --production --onlyAllow "MIT;ISC;Apache-2.0;BSD-2-Clause;BSD-3-Clause"
If a dependency flips to GPL tomorrow, I'd rather find out from a CI check than from a client's lawyer.
Second, when I ask an agent to "borrow" a pattern from someone else's repo, the origin goes into the commit message. One line. Who wrote it, where it came from.
It costs nothing. It's also the exact thing laundering removes.
I made a similar argument about who actually gets paid in open source. Money is one way to give back. Attribution is the free one, and AI is making it the first thing to go.
Attribution Is the Whole Contract
Asahi's move is messy. The consent question is real. The bridges with OpenBSD are real. Whatever happened with the forks is still being argued in public.
I still think they're right.
When a model can rewrite five years of reverse-engineering in an afternoon, a license that only asks for a notice is asking for the one thing the model throws away first.
Use AI to build faster. Don't use it to erase who built it first. Credit your sources.


