Asahi Linux drops MIT for GPL over AI-rewritten code

Asahi Linux is leaving the MIT license because people used AI to launder its code. In its Linux 7.3 progress report on November 7, the project that ports Linux to Apple Silicon Macs said it will begin to move all of its repositories to GPL-2.0-or-later. The stated reason: code still in development was taken from contributors' personal forks, then published without credit or rewritten with LLM help to hide where it came from. If your business publishes code, or builds on open source, this open-source license change is worth five minutes.

What actually happened

Per the Asahi report, written by developer James Calligeros:

• The change. Asahi used MIT for as much code as possible. It now says all Asahi code will use strong copyleft licenses only, starting with GPL-2.0-or-later. The report says the process has begun. It gives no completion date.
• The reason. The project says it saw multiple attempts to use its permissive license to "hijack our work." Feature code was "lifted straight out of our personal forks" before release. Some was "lazily rewritten with LLM assistance to obfuscate its origin." The report names no one.
• The precedent. Asahi points to WINE, which moved from MIT to the LGPL in 2002 to stop proprietary forks.
• The pushback. It's FOSS reports that an OpenBSD developer criticized the move, because the report does not say how earlier contributors agreed to the change. OpenBSD's Apple Silicon support also uses Asahi code.

Why it matters for your business

Three lessons, and none of them need a lawyer to start.

A public branch is published code. Asahi's work in progress was in personal forks on public hosts. Anyone could read it, copy it, or feed it to a model. If your unreleased product code sits in a public repo "for now," move it to a private one today.

An LLM rewrite does not clean the license. Asahi's complaint is about attribution and copying, not only legal terms. If your team asks an AI tool to "rewrite this library so we can use it," the code you get is still derived from that library. Treat it as the original license, and keep the attribution.

Your dependencies can change licenses. When a project moves from MIT to GPL, new versions come with new duties. If you ship software to customers, a GPL dependency can change what you must give them. Add a license check to your build so a version bump cannot change your obligations without notice.

Sources: Asahi Linux: Progress Report: Linux 7.3, It's FOSS.