Apache License, Version 2.0 with LLVM Exception

Also known as Apache 2.0 with LLVM exception, Apache License 2.0 with LLVM Exception, Apache-2.0 WITH LLVM-exception, Apache-2.0-with-LLVM-exception, LLVM Exception.

Commercial use: allowed
Share alike: not required
Attribution: required (keep the copyright and license notices)

Compare with… Add to the compatibility check Download JSON-LD Turtle RDF/XML Text

Write this as a license text (needs an account) DALICC reads the model above and writes what it permits, requires and prohibits in plain English. Without an account, the Text download above writes the model out from the vocabulary.

Canonical URI https://dalicc.net/licenselibrary/Apache-2.0-with-LLVM-exception

Permissions

Change license by library convention
Duties
- Use a compliant license by library convention
Charge distribution fee from the text
Commercial use from the text
Derivative works from the text
Derive from the text
Duties
- Attribution from the text
- Modification notice from the text
- Notice from the text
Display from the text
Distribute from the text
Duties
- Attribution from the text
- Notice from the text
Excepted combination from the text
Grant use from the text
Modified works from the text
Modify from the text
Duties
- Attribution from the text
- Modification notice from the text
- Notice from the text
Patent grant from the text
Present from the text
Reproduce from the text

Prohibitions

Promote from the text

License-wide duties

This license states no duties that apply to the work as a whole.

What applies by default

The statements above are the library's reading of this license: each is marked with the sentence it rests on, or as a library convention where the text is not explicit. The statements below are the ones the DALICC reasoner supplies for acts the license says nothing about, from the default rules of the dependency graph it reasons with. Each one names the legal source it rests on. None of it is in the record.

No default rule of that graph reaches this license: it speaks about every act the rules are about.

Further terms

These are the things the license says about itself beyond the acts it permits, forbids and requires: when it ends, how long there is to put a breach right, which law governs it, and so on. A term that comes from the DALICC vocabulary links to its definition.

Patent license ends if you sue: Yes. Not a ban on suing: a patent claim over the work ends the patent license, or the whole license, as the text provides.
Reciprocity scope: the Software, not portions of it embedded into an Object form by compiling your source code

Clauses

Warranty disclaimer

Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

Limitation of liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

Accepting warranty or additional liability

While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

Additional clauses

---- LLVM Exceptions to the Apache 2.0 License ---- As an exception, if, as a result of your compiling your source code, portions of this Software are embedded into an Object form of such source code, you may redistribute such embedded portions in such Object form without complying with the conditions of Sections 4(a), 4(b) and 4(d) of the License. In addition, if you combine or link compiled forms of this Software with software that is licensed under the GPLv2 ("Combined Software") and if a court of competent jurisdiction determines that the patent provision (Section 3), the indemnity provision (Section 9) or other Section of the License conflicts with the conditions of the GPLv2, you may retroactively and prospectively choose to deem waived or otherwise exclude such Section(s) of the License, but only in their entirety and only with respect to the Combined Software.

Info

Target asset types: Creative work (i.e. text, picture, sound, movie), Dataset, Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://spdx.org/licenses/LLVM-exception.html
Legal code: http://www.apache.org/licenses/LICENSE-2.0
This description is published under: Creative Commons Attribution 4.0 International
Publisher: The Apache Software Foundation
SPDX identifier: Apache-2.0 WITH LLVM-exception on the SPDX license list
DALICC identifier: Apache-2.0-with-LLVM-exception

This record is published under CC BY 4.0. Credit it as: DALICC License Library, DALICC - Verein zur Förderung der Rechtssicherheit in der Datenbewirtschaftung, https://dalicc.net, CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). The license it describes belongs to its publisher.

Use this license

Everything below is generated from this record. Replace the example address with the address of your own work.

JSON sidecar

{
  "license-uri": "https://dalicc.net/licenselibrary/Apache-2.0-with-LLVM-exception",
  "license-title": "Apache License, Version 2.0 with LLVM Exception",
  "spdx-id": "Apache-2.0 WITH LLVM-exception",
  "attribution": "Copyright (c) [year] [copyright holder]",
  "asset": null,
  "generated-by": "DALICC"
}

RDF, Turtle

@prefix cc: <http://creativecommons.org/ns#> .

<https://example.org/my-work>
    cc:license <https://dalicc.net/licenselibrary/Apache-2.0-with-LLVM-exception> .

RDF, JSON-LD

{
  "@context": {
    "cc": "http://creativecommons.org/ns#"
  },
  "@id": "https://example.org/my-work",
  "cc:license": {
    "@id": "https://dalicc.net/licenselibrary/Apache-2.0-with-LLVM-exception"
  }
}

HTML attribution

<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/Apache-2.0-with-LLVM-exception" rel="license">Apache License, Version 2.0 with LLVM Exception</a>.</p>

This license asks for attribution, so the credit line is part of it.

Badge

Markdown

[![License: Apache License, Version 2.0 with LLVM Exception](https://dalicc.net/license-library/Apache-2.0-with-LLVM-exception/badge.svg)](https://dalicc.net/license-library/Apache-2.0-with-LLVM-exception)

HTML

<a href="https://dalicc.net/license-library/Apache-2.0-with-LLVM-exception"><img src="https://dalicc.net/license-library/Apache-2.0-with-LLVM-exception/badge.svg" alt="License: Apache License, Version 2.0 with LLVM Exception"></a>

Review

Written from the license text by: Giray Havur
Written on: 2026-09-22
Second review: not yet done
Record changed since this review: yes (version 2, 2026-09-24)
Findings: 14 recorded, 13 applied to the record, 0 proposed

The record models the Apache licence version 2.0 as the LLVM project distributes it, with the LLVM exception added. It keeps every statement of the Apache-2.0 record and adds one permission for the portions of the software that a compiler embeds in object code, which may be redistributed without the notice conditions of sections 4(a), 4(b) and 4(d). The second paragraph of the exception, which lets you deem a conflicting section waived when the result is combined with software under GPL version 2, has no term in the vocabulary and is quoted instead.

14 findings

info Rubric 1 spdx:licenseId applied

File name, record identifier, IRI local name and title agree. spdx:licenseId carries the SPDX expression "Apache-2.0 WITH LLVM-exception": the base identifier, one space, WITH in capitals, one space, the exception identifier. No record in the library carried an expression before, so the SPDX mapping and the spdx route have to accept the space and the keyword.
info Rubric 1 cc:legalcode applied

cc:legalcode points at the text of the base licence, http://www.apache.org/licenses/LICENSE-2.0, because that is the licence the record models. dct:source points at the SPDX page of the exception, https://spdx.org/licenses/LLVM-exception.html, because that is where the additional permission is published.
info Rubric 2 odrl:target applied

odrl:target is the one the Apache-2.0 record carries: dalicc:CreativeWork, dcmitype:Dataset and dcmitype:Software. The licence speaks of a "Work" of authorship of any kind, so the wide target is the base record's reading and the exception gives no reason to narrow it.
major Rubric 3 odrl:permission applied

The exception reads: "As an exception, if, as a result of your compiling your source code, portions of this Software are embedded into an Object form of such source code, you may redistribute such embedded portions in such Object form without complying with the conditions of Sections 4(a), 4(b) and 4(d) of the License." The embedded portions are material that the redistribution conditions no longer reach, which is the permission dalicc:exceptedCombination.
info Rubric 3 odrl:permission applied

Every permission of Apache-2.0 is kept, in the same place and with the same duties. An exception adds an additional permission to a licence; it never takes a granted right away.
info Rubric 4 odrl:prohibition applied

The two prohibitions of the base record are kept: dalicc:promote, supported by section 6 of the licence, and dalicc:patentRetaliationTermination, supported by section 3. The exception does not touch either, although it lets you waive section 3 in one narrow case, which the next finding records.
info Rubric 5 odrl:duty applied

The attribution, notice and modification-notice duties stay on odrl:distribute, odrl:modify and odrl:derive. The exception lifts them for one kind of material only, the portions embedded in object form, and the record says that in dalicc:reciprocityScope rather than by removing a duty.
info Rubric 6 dalicc:additionalClauses applied

The exception text is quoted verbatim as one literal, taken from https://raw.githubusercontent.com/spdx/license-list-data/main/text/LLVM-exception.txt. Line breaks and the indentation of the source file are collapsed to single spaces, which is how every clause literal in the library is written; the wording is untouched. The warranty disclaimer and the liability limitation are the ones the base record quotes from the base licence.
info Rubric 7 cc:jurisdiction applied

cc:jurisdiction stays dalicc:worldwide and dalicc:validityType stays dalicc:perpetual: the exception names no territory and no term. The termination clause of the base licence still applies, and the record says no more about it than the base record does.
minor Rubric 7 dalicc:reciprocityScope applied

dalicc:reciprocityScope is defined as how far a share-alike condition reaches. Apache 2.0 has no share-alike condition, so here the literal names how far the redistribution conditions of section 4 reach after the exception. That is the same question one step weaker, and no other annotation asks it.
gap Rubric 8 dalicc:exceptedCombination applied

The exception carves the combination out of the condition of the licence, not out of its grant. dalicc:exemptedMaterial says the opposite and is prohibited on OGL-UK-1.0, OGL-UK-2.0 and NLOD-2.0, where it means material the licence never granted. The vocabulary defines dalicc:exceptedCombination for this side of it since 2026-09-23, and the record carries it as a permission.
gap Rubric 8 dalicc:additionalClauses none

The second paragraph cannot be expressed: "if you combine or link compiled forms of this Software with software that is licensed under the GPLv2 ("Combined Software") and if a court of competent jurisdiction determines that the patent provision (Section 3), the indemnity provision (Section 9) or other Section of the License conflicts with the conditions of the GPLv2, you may retroactively and prospectively choose to deem waived or otherwise exclude such Section(s) of the License, but only in their entirety and only with respect to the Combined Software." It is a conditional waiver of the licence's own sections, granted to make the result compatible with another licence. Proposed term: dalicc:conflictingTermWaiver, an annotation naming the sections that may be waived and the licence the conflict is measured against.
info Rubric 9 record applied

app.services.composer.consistency_check with the default dependency graph reports 0 conflicts for this record. dalicc:exceptedCombination takes part in no dependency relation, so it neither creates nor hides one.
info Rubric 10 record applied

The nearest sibling is Apache-2.0 itself. This record differs from it in five statements: the SPDX expression, the exception text in dalicc:additionalClauses, the dalicc:exceptedCombination permission, dalicc:reciprocityScope, and dalicc:variantKind "exception" with dalicc:variantOf. Everything else is copied, including the patent grant and the patent retaliation prohibition, which travel together.

Report an issue The review record as JSON The review checks the model against the license text. It is not legal advice.

History

This license model has 2 versions. Version 2 is the one served today; every earlier version keeps its own address, so a conclusion drawn from one of them can still be checked against it.

Version 2 current2026-09-24 Giray Havur

The changes since version 1 recorded which sentence of the text each statement rests on and named the license the record itself is published under.

View version 2 JSON-LD Turtle RDF/XML
6 changes
- changed permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]
  
  was permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]
  
  Manual edit The statement is marked as a library convention, family rule 15: Permissive records permit relicensing: the text does not state it in as many words. Its duty dalicc:compliantLicense is marked as a library convention, family rule 15: Permissive records permit relicensing.
- changed permission odrl:derive with duties [cc:Attribution, cc:Notice, dalicc:modificationNotice]
  
  was permission odrl:derive with duties [cc:Attribution, cc:Notice, dalicc:modificationNotice]
  
  Manual edit Its duty cc:Attribution quotes "If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear." Its duty cc:Notice quotes "You must give any other recipients of the Work or Derivative Works a copy of this License; and"
- changed permission odrl:distribute with duties [cc:Attribution, cc:Notice]
  
  was permission odrl:distribute with duties [cc:Attribution, cc:Notice]
  
  Manual edit Its duty cc:Attribution quotes "If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear." Its duty cc:Notice quotes "You must give any other recipients of the Work or Derivative Works a copy of this License; and"
- changed permission odrl:modify with duties [cc:Attribution, cc:Notice, dalicc:modificationNotice]
  
  was permission odrl:modify with duties [cc:Attribution, cc:Notice, dalicc:modificationNotice]
  
  Manual edit Its duty cc:Attribution quotes "If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear." Its duty cc:Notice quotes "You must give any other recipients of the Work or Derivative Works a copy of this License; and"
- changed prohibition dalicc:promote
  
  was prohibition dalicc:promote
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file."
- added dct:license <https://creativecommons.org/licenses/by/4.0/>
  
  Manual edit Every record is published under CC BY 4.0. cc:license names the record DALICC keeps of that licence; dct:license now names it by the address Creative Commons publishes it at, so that a consumer matching the canonical IRI finds it.
Version 1

Created from the license text on 2026-09-22 (Apache Software Foundation (1.1, 2.0)).

View version 1 JSON-LD Turtle RDF/XML

Every change names the reason behind it: a finding of the content review, one of its library-wide decisions, the metadata that review wrote onto every record, or a hand edit. None of it is legal advice.

Nothing on this page is legal advice. What a license means is decided by its text; ask a legal advisor before you rely on it.