Apply the rules
Inspect a real distribution using Apache License 2.0. Identify its license version, required notices, upstream dependencies and any unresolved permissions.
Licenses / Knowledge library
Apache License 2.0
Understand Apache License 2.0: permissions, conditions and limitations.
Why learn Apache License 2.0?
Make informed reuse and redistribution decisions under Apache License 2.0; this lesson is not legal advice.
The problem it solves
Explains the obligations that a license label alone can hide. Verify the exact version and upstream terms.
Where it came from
What extra intellectual-property permission is explicit in Apache-2.0? (Apache License 2.0) A contributor patent license. When distributing modified Apache-2.0 files, what must they carry? (Apache License 2.0) Prominent notices that they were changed. How must a relevant Apache NOTICE file be handled on redistribution? (Apache License 2.0) Preserve the applicable attribution notices. Does Apache-2.0 generally grant rights to use contributor trademarks? (Apache License 2.0) No; trademark rights are excluded except limited descriptive use. What can happen if a licensee brings specified patent litigation under Apache-2.0? (Apache License 2.0) The patent license can terminate.
- What extra intellectual-property permission is explicit in Apache-2.0? (Apache License 2.0) A contributor patent license.
- When distributing modified Apache-2.0 files, what must they carry? (Apache License 2.0) Prominent notices that they were changed.
- How must a relevant Apache NOTICE file be handled on redistribution? (Apache License 2.0) Preserve the applicable attribution notices.
- Does Apache-2.0 generally grant rights to use contributor trademarks? (Apache License 2.0) No; trademark rights are excluded except limited descriptive use.
- What can happen if a licensee brings specified patent litigation under Apache-2.0? (Apache License 2.0) The patent license can terminate.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- What extra intellectual-property permission is explicit in Apache-2.0? (Apache License 2.0)
- When distributing modified Apache-2.0 files, what must they carry? (Apache License 2.0)
- How must a relevant Apache NOTICE file be handled on redistribution? (Apache License 2.0)
- Does Apache-2.0 generally grant rights to use contributor trademarks? (Apache License 2.0)
- What can happen if a licensee brings specified patent litigation under Apache-2.0? (Apache License 2.0)
More ways to practice
Documentation and sources
- Official specification / license documentation (www.apache.org)
Catalog research notes
- Learning notes checked October 13, 2026. Consult the official source for subsequent changes.
Connect the ideas
Explore next
MIT LicenseModel licensing and upstream termsBSD 2-Clause LicenseBSD 3-Clause LicenseGNU GPL v3GNU AGPL v3Mozilla Public License 2.0CC BY 4.0CC BY-SA 4.0CC BY-NC 4.0CC0 1.0Llama 2 Community LicenseLlama 3.3 Community LicenseGemma Terms of UseHealth AI Developer Foundations termsLlama 3.1 Community LicenseLlama 3.2 Community LicenseCreativeML Open RAIL-MCreativeML Open RAIL Plus Plus M
Real World Example
Open-Source Data Pipeline Integration
A data analytics firm building a proprietary processing engine that incorporates open-source libraries.
The business problem
The firm needs to integrate third-party code without risking their own intellectual property or facing legal ambiguity regarding patent rights.
How this topic solves it
The Apache License 2.0 provides a clear, permissive framework that allows the firm to use, modify, and distribute the code while maintaining a perpetual, royalty-free patent grant from contributors.
- Include a copy of the Apache License 2.0 in the distribution package.
- Retain all original copyright, patent, and trademark notices in the source code.
- Add prominent notices to any modified files indicating that changes were made.
- Include the original NOTICE file if one exists in the source distribution.
Entities and their relationships regarding license compliance.
Original author of the code
The original source code
The entity using the code
Modified version of the code
- Contributor → grants license → Work
- Work → used by → Firm
- Firm → creates → Derivative Work
- Derivative Work → must retain notices from → Work
Expected business outcome
The firm can safely integrate the library into their proprietary engine, ensuring compliance while retaining the ability to sublicense their own derivative work under different terms.
Limitations and checks
The license does not grant permission to use the trademarks of the original licensor. Compliance is checked by verifying that all attribution notices are preserved and that no trademarked names are used in a way that implies endorsement.