Asahi Linux, the project bringing Linux to Apple Silicon Macs, announced on November 7, 2026 that it is relicensing all of its repositories from the permissive MIT license to the GNU General Public License v2 or later. The stated reason: bad actors were using AI tools to steal unreleased code from developers' personal forks, then rewriting it just enough to obscure its origin.
What Happened
Asahi's developers noticed that code still in development — sitting in personal forks, not yet merged — was appearing in other projects. The alleged mechanism: AI language models were being used to rewrite the stolen code at a surface level, changing variable names and restructuring logic while preserving the underlying work. The technique has been dubbed LLM-assisted license laundering.
Two projects were cited in coverage as being involved: Aurora Silicon's Borealis Vulkan driver and Gravity Linux, a Fedora-based distribution. Asahi has not named anyone directly in its official statements.
Why GPL Instead of MIT
MIT is one of the most permissive licenses available. Anyone can take MIT-licensed code, modify it, and release it under a completely different license — including a proprietary one. That permissiveness was fine when the main concern was legitimate downstream use.
GPL is different. It requires that any derivative work also be distributed under GPL. If someone takes GPL-licensed Asahi code and ships it in their own project, that project must also be open-sourced under GPL. The copyleft provision makes it much harder to launder code, because publishing the derivative forces disclosure.
The Controversy
The move isn't without criticism. OpenBSD developer Bryan Steele publicly noted that relicensing was done without the consent of all prior contributors — a legally significant point, since copyright belongs to each contributor individually. Asahi's developers hold copyright over their own contributions, but earlier contributors who submitted code under MIT may not have agreed to a GPL relicense.
As of the announcement, some Asahi repositories — including asahi-installer — still showed MIT terms in the main branch, suggesting the transition is still in progress. Historical MIT-licensed snapshots remain available to downstream users under their original terms.
The Bigger Picture
The Asahi situation is part of a growing tension across open source: permissive licenses were designed for a world where copying code required human effort. AI tools lower that effort close to zero — making automated, large-scale code extraction a practical threat for projects that weren't thinking about it.
Whether GPL is the right answer is debated. But Asahi's move is an early, concrete example of an open-source project updating its licensing strategy in direct response to AI-assisted misuse. The Git project is currently weighing its own vote on LLM-written contributions policy, and other major open-source projects are watching these precedents closely.
Expect more projects to have this conversation in 2027.