Asahi Linux Adopts GPL to Fight AI-Driven License Laundering

Asahi Linux announced in its Linux 7.3 Progress Report that it is transitioning all project repositories from the permissive MIT license to the GNU General Public License version 2 or later (GPLv2+). The project, responsible for reverse engineering Apple Silicon hardware to make Linux viable on modern Macs, made the strategic decision after detecting bad-faith actors lifting in-development feature code directly from contributors’ personal forks. These actors then used Large Language Models (LLMs) to rewrite and obfuscate the code’s lineage, attempting to aggressively monetize Linux-on-Apple-Silicon distributions without attribution or upstream contributions. In response, maintainers have abandoned permissive licensing in favor of copyleft protections.

Automated Code Laundering and the Collapse of Permissive Trust

For several years, the Asahi Linux project maintained its foundational code under the permissive MIT license. That decision was intentional: maintainers wanted other open-source operating systems, particularly BSD-based projects such as OpenBSD, to freely adapt their hardware enablement work. However, maintainers discovered that permissive terms created vulnerabilities when confronted with commercial opportunism aided by generative artificial intelligence.

According to project maintainers, bad-faith actors were identifying unmerged pull requests and experimental branches in developer forks, extracting in-progress driver logic, and using generative models to launder the code. Prior to the widespread availability of LLMs, code laundering required tedious manual labor: engineers had to systematically refactor syntax, rename variables, and alter control flow by hand to conceal original authorship. Generative AI tools have lowered the cost and friction of this obfuscation to near zero, enabling automated rewriting that strips away structural fingerprints while preserving underlying reverse-engineered hardware interfaces.

The MIT license permits commercial use and closed-source redistribution provided that copyright and permission notices remain intact. However, maintainers noted that MIT provides no contractual mechanism or structural barrier to prevent bad-faith actors from laundering code through an LLM to erase attribution and launch closed, monetized products. To explain the shift, Asahi Linux drew a direct parallel to the historical precedent set by the WINE project in 2002, which migrated from MIT to the GNU Lesser General Public License (LGPL) after proprietary vendors repeatedly incorporated WINE code into closed commercial products without sharing improvements with the community.

Hardware Milestones, Clean-Room Rules, and BSD Ecosystem Impact

The relicensing announcement coincided with the project’s Linux 7.3 release, which achieved general availability (GA) for M3 Apple Silicon hardware support alongside significant upstreamed Thunderbolt improvements. The technical achievement underscores the immense engineering effort involved in documenting Apple’s undocumented system architecture, custom power management, and graphics silicon.

To safeguard the integrity of that reverse engineering, Asahi Linux maintains a strict ban on AI-generated code contributions. Project leadership established this policy to ensure that all drivers adhere to clean-room engineering standards and remain free from tainted or infringing training data ingested by commercial models. The irony highlighted by maintainers is that while Asahi barred AI tools from contributing to its codebase, external actors utilized those same tools to extract and relicense their work without consent.

The transition to GPLv2+ has raised immediate technical and architectural hurdles for downstream collaborators, most visibly within the BSD ecosystem. OpenBSD’s burgeoning Apple Silicon platform relies directly on Asahi’s m1n1 stage-one bootloader and low-level hardware support. Because the OpenBSD project operates under strict permissive licensing guidelines, incorporating GPL-licensed code into the base system is impermissible under their project bylaws.

From a legal perspective, the transition does not operate retroactively. Existing releases published under the MIT license—including m1n1 up to version 1.9.9—remain permanently licensed under MIT and may continue to be used, adapted, or distributed under those terms. However, all future development, bug fixes, and feature additions across Asahi’s repositories will strictly carry GPLv2 or later licensing, requiring downstream distributions to choose between freezing on older MIT versions, maintaining their own clean-room ports, or isolating the bootloader as an external component.

What happens next

Asahi Linux maintainers are actively executing the repository-wide migration across their GitHub and internal trees, updating headers and license files to GPLv2+. The move marks one of the first high-profile instances where an open-source infrastructure project has transitioned to copyleft specifically to counter AI-assisted license laundering rather than cloud service providers repackaging software as managed infrastructure.

Downstream operating system teams, including OpenBSD developers, must now assess how to handle hardware enablement updates moving forward. While existing binary builds of m1n1 1.9.9 remain viable for boot initialization, subsequent hardware support for newer Apple revisions will be subject to copyleft conditions. Technical teams will be monitoring whether other systems projects experiencing LLM-driven scraping and attribution evasion follow Asahi’s lead in abandoning permissive licenses to protect their developer commons.