The LLVM project has proposed calling its long-running relicensing effort complete. According to a post published on its forums on November 19, 2026, more than 99.5% of all code ever contributed is now covered by the Apache 2.0 License with LLVM Exceptions, has been removed, or is too small to be protected by copyright.
Key points of LLVM’s relicensing in 20 seconds
- Over 1,300 individuals and about 100 companies and organisations signed agreements.
- New code has used Apache-2.0 WITH LLVM-exception since January 19, 2019.
- License files and headers will be updated, landing with LLVM 25.
Administración de Sistemas has published a detailed Spanish-language look at LLVM’s relicensing and history. For sysadmins and developers nothing changes in day-to-day use: Clang, LLD, LLDB and the rest of the toolchain work as before. What changes is legal certainty for anyone who ships or embeds LLVM.
What was announced
The post, written by forum user kbeyls, describes the effort as nearly done and proposes treating it as complete. Code not covered by an agreement is handled by three rules: contributions of 10 lines or fewer are considered too small for copyright, code no longer in the repository (such as removed backends) is not counted, and vendored third-party code keeps its own license. Past contributors who have not signed and object can email [email protected], and SPDX identifiers will be added to files that still contain copyrightable amounts of their code.
Next comes the paperwork: LICENSE files, developer policy, FAQ, READMEs, source headers, release packaging and the LLVM Foundation website will be updated, and the “relicensing in progress” wording will become a historical note. The post says the LLVM 24 release branch is expected in early January 2027, with these changes shipping in LLVM 25.
Why LLVM changed its license
The debate began in October 2015, when LLVM creator Chris Lattner proposed on llvm-dev relicensing the whole project under Apache 2.0 with an exception. The original University of Illinois/NCSA license was a permissive BSD-style license, but it lacked an explicit patent grant, applied differently to the compiler (UIUC only) and the runtime libraries (UIUC and MIT), and carried a binary attribution requirement awkward for runtime code linked into users’ programs.
Apache 2.0 brings a well-understood patent grant, but it also requires attribution and raised GPLv2 compatibility concerns. The LLVM exceptions address both: one removes the attribution requirement for LLVM code that ends up in compiled programs, and the other removes the potential incompatibility with GPLv2 code. The final wording was settled in 2017 after further rounds of proposals, and the SPDX identifier is Apache-2.0 WITH LLVM-exception. Not everyone was happy: parts of the BSD community preferred shorter licenses such as BSD or ISC.
A short history and where releases stand
LLVM began in 2000 as a research project at the University of Illinois at Urbana-Champaign, led by Chris Lattner and Vikram Adve. After Lattner joined Apple in 2005, Apple backed the project and introduced Clang in 2007, which went on to replace GCC in Xcode. FreeBSD adopted Clang as its default compiler, Google uses LLVM across Android and Chrome, the Linux kernel can be built with Clang, and languages such as Swift, Rust, Julia and Zig build on it. LLVM received the ACM Software System Award in 2012, and the LLVM Foundation has governed it since 2014.
The project ships two major releases a year with fortnightly point releases. LLVM 22 was the first-half 2026 release, ending with 22.1.8 in June. LLVM 23 branched on July 14, 2026, and 23.1.0 arrived on August 25 with AMD Zen 6, NVIDIA Rigel and partial C++26 support. The latest point release is 23.1.6, out on November 17, with 23.1.7 and 23.1.8 scheduled for December 1 and 15.
Frequently asked questions
What license does LLVM use?
The Apache 2.0 License with LLVM Exceptions (SPDX: Apache-2.0 WITH LLVM-exception). Before 2019 it used the UIUC/NCSA license.
Does this affect programs I compile with Clang?
No. One of the LLVM exceptions means LLVM code that ends up in your compiled program does not require attribution.
What is the latest LLVM release?
The current stable series is LLVM 23, with 23.1.6 released on November 17, 2026.
Sources:
