What is License Compatibility
You'll learn: How to determine whether different open-source licenses can legally coexist in the same software project.
The Core Problem
License compatibility addresses a critical question: if your project uses multiple dependencies or components—each under different licenses—can they legally be combined, or do their terms conflict?
Think of licenses like puzzle pieces. Some fit together perfectly, some require special positioning, and some simply won't connect at all. When licenses are compatible, their requirements don't contradict each other. When they're incompatible, combining code under those licenses would violate at least one license's terms.
Why Compatibility Matters
Imagine you want to build an application using:
- A library under the MIT License (permissive)
- Another library under the Apache 2.0 License (permissive with patent grants)
- A component under the GPL v3 (copyleft)
The MIT and Apache 2.0 components can generally be combined with GPL v3 code—but the entire combined work must then be distributed under GPL v3 terms, because GPL's copyleft nature "infects" the whole. However, you cannot combine GPL v3 code with proprietary closed-source code in the same derived work.
Common Compatibility Scenarios
Easy combinations:
- MIT + BSD + Apache 2.0 → All permissive, fully compatible
- LGPL library linked by proprietary code → LGPL allows this
Problematic combinations:
- GPL v2-only code + GPL v3 code → Incompatible version mismatch
- GPL code + proprietary code in same binary → Violates GPL terms
Key Takeaway: License compatibility determines whether you can legally combine code from different sources; incompatible licenses force you to choose between components, relicense, or seek exceptions from copyright holders.