Skip to content
Theme
OnDevice Tools

SoftwareOpen Source & Linux

LLVM relicensing effort ends after eight years at 99.5% coverage

The LLVM project has declared its eight-year relicensing programme complete, with more than 99.5% of code ever added now covered, too minor for copyright or removed. Contributors who object to the Apache-2.0 terms can still contact the project about older code.

Illustration of LLVM source files with licence headers and a completed relicensing notice

Key takeaways

  • LLVM has closed its relicensing programme after eight years.
  • Code added since 19 January 2019 uses Apache-2.0 WITH LLVM-exception.
  • Over 99.5% of all code ever added is covered, too minor for copyright or removed.
  • Older contributors who object to the new terms can still request an SPDX identifier.
In this article
  1. What LLVM has announced
  2. Why older code needed permission
  3. How much code is covered
  4. What older contributors can still do

What LLVM has announced

The LLVM relicensing effort is over, according to a summary from Kristof Beyls on the project's discussion forum that was reported by LWN.net on 20 November 2026. The project has spent eight years asking past contributors for permission to move their code to a new licence. Beyls says the work is now a success and that the project is closing the programme.

New contributions have arrived under Apache-2.0 WITH LLVM-exception since 19 January 2019. Code added before that date sat under older terms, so the project needed agreement from the authors before it could change the licence. The summary marks the end of that request process.

Why older code needed permission

Illustration: code, news and the labels Kristof Beyls, LLVM

Before 19 January 2019, LLVM used the UIUC/NCSA licence, with MIT terms for some runtime libraries. Those terms differed from the Apache-2.0 WITH LLVM-exception licence used for newer code. Relicensing means changing the legal terms that apply to existing work, and the project needed permission from those authors to make the change. The project therefore had to track down past contributors and ask each one to agree.

The effort began in 2018, a year before the new contribution terms took effect. The gap explains why the project could not simply switch the whole codebase at once. Code from the earlier period needed individual clearance, while new code already carried the intended terms.

How much code is covered

The summary puts coverage at over 99.5% of every line ever added to LLVM. Those lines either sit under the new terms, fall below the threshold for copyright protection, or have been deleted from the codebase. That leaves a very small remainder outside the three categories.

LLVM has chosen to stop rather than pursue every remaining fragment indefinitely. The summary describes the effort as complete and says the project is winding it up. The decision means the final fraction will not be tracked to the last line.

What older contributors can still do

Contributors who added code before 19 January 2019 can still contact the project if no relicensing agreement is in place. This applies when they object to their work being distributed under Apache-2.0 WITH LLVM-exception. The route lets them make sure the correct SPDX licence identifier appears on that code.

An SPDX identifier is a short standard code that records which licence applies to a file or component. The offer gives remaining contributors a way to flag older work even though the main programme has ended. It also gives the project a way to keep licence records accurate for code that remains in the repository.

Sources

  1. Beyls: Wrapping up LLVM's relicensing effortLWN.net

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.