Asahi Linux, the volunteer project that makes Linux run natively on Apple Silicon Macs, is abandoning its permissive licensing model and moving every one of its repositories to the GNU General Public License version 2 or later. The reason, according to an announcement reported by It's FOSS on Saturday: bad actors have been lifting the project's unreleased code — some of it straight out of developers' personal forks — and running it through large language models to disguise where it came from.
The story is one of the most concrete cases yet of what open-source maintainers are calling AI-assisted "code laundering," and it is drawing significant attention on developer forums, including a busy Hacker News discussion over the weekend. For more context on this story, see our ongoing AI news.
What Code Laundering Means
Code laundering, sometimes called license laundering, is the practice of taking someone else's code and passing it through a transformation that hides its origin, so it can be reused without honoring the original license or crediting the author. Before AI, that meant painstaking manual rewriting: renaming variables, reshuffling functions, restructuring logic line by line until the provenance was obscured.
Large language models have collapsed the cost of that process. A model can rewrite a codebase in a different style in minutes, stripping the recognizable fingerprints that maintainers used to rely on. The Asahi team says it became aware some time ago of multiple attempts to exploit its permissive licensing in exactly this way, including the most extreme cases: feature code that was still under development, lifted from developers' personal forks before it was ever publicly released, then published without credit.
According to the reporting, the goal of at least some of those actors was blunt — "replacing the project and aggressively monetising Linux on Apple Silicon."
Why MIT Left Asahi Exposed
Asahi Linux had historically licensed most of its own code under MIT, one of the most permissive licenses in open source. MIT requires only that the original copyright notice be preserved; it does not require derivative works to be shared back, or improvements to remain open. That openness made it easy for BSD projects and commercial vendors to adopt Asahi's work — and, it turns out, equally easy for bad-faith actors to abuse it. As the project's report noted, the MIT license explicitly allows this kind of reuse and has no carveouts to protect against bad faith actors.
By moving to GPLv2-or-later, Asahi is adopting strong copyleft: anyone who distributes modified versions of the code must release the source of those modifications under the same license. Code passed through an LLM is still derivative of the original, so the license obligations survive the rewrite — at least in principle.
Learning From WINE's History
The Asahi team is explicit about the precedent it is following. WINE, the compatibility layer that lets Linux users run Windows applications, spent its early years under the MIT license. Through the late 1990s and early 2000s, companies took WINE's code, built proprietary forks on top of it and sold them commercially, contributing little or nothing back. In 2002, the WINE project relicensed its codebase to the LGPL to discourage proprietary forks and push commercial vendors to upstream their changes.
Two decades later, Asahi is making the same calculation with a new twist: the adversary is no longer just a proprietary vendor, but anyone with an LLM and an incentive to strip attribution.
Open Questions
The announcement leaves several issues unresolved, as It's FOSS points out. Asahi has not named any of the actors involved. It has not detailed how existing contributions will be relicensed, or whether every past contributor has agreed to the change — a legally meaningful question, since contributors hold copyright on their contributions unless an agreement says otherwise. The practical enforceability of GPL obligations on machine-rewritten code is also largely untested.
What is clear is intent. Every Asahi Linux repository will move to GPL v2 or later, and the project has decided that permissiveness is a luxury it can no longer afford. Whether every downstream user — from BSD packagers to commercial vendors who relied on MIT terms — will welcome the change is another matter, and some friction is inevitable.
A Warning for Permissive Open Source
The episode lands amid a broader anxiety in the open-source world about AI-driven extraction — from publishers asking the EU to halt Meta's AI crawling to benchmark studies showing coding agents gaming evaluation suites. For maintainers of small, high-value projects, the lesson of Asahi's move is that provenance protections that made sense in a human-copying era may not survive contact with models that can rewrite anything in seconds.
For the rest of the ecosystem, Asahi's decision is a live experiment: if copyleft proves effective at deterring AI-assisted laundering, expect more projects to follow WINE's path — and Asahi's.
---
Stay Ahead of AIGet the latest AI news, analysis, and breakthroughs — all in one place.
Read more AI news →
