Open-source license compatibility checker
Select the licenses you are combining and how you distribute the result. You get the verdict, the resulting work's license and the obligations, from a reviewed dataset of 24 common licenses.
Pick the licenses. Read the answer.
Every verdict comes from one reviewed dataset. Conditional answers say what they depend on.
Scan a dependency tree
Paste a package-lock.json or an SBOM. One verdict, and the package behind each conflict.
"node_modules/tslib": { "license": "0BSD" } "node_modules/lru-cache": { "license": "BlueOak-1.0.0" } "node_modules/argparse": { "license": "Python-2.0" }Open the scanner
Every pair, one grid
24 licenses, 276 pairs. Green combines, red conflicts, amber depends.
From no obligations to network copyleft
Five categories drive the generic rules. Hover or tab into a category to open it.
Permissive
Permissive
9 licenses
Two of these together: Combine freely; retain all notices. Result can be relicensed (kept proprietary) downstream.
Weak copyleft
Weak copyleft
7 licenses
Two of these together: Usually fine since each only governs its own files/library, but check the specific pair (EPL has GPL-style frictions).
Strong copyleft
Strong copyleft
4 licenses
Two of these together: Same GPL version family is fine; GPLv2-only vs GPLv3 is incompatible.
Network copyleft
Network copyleft
2 licenses
Two of these together: Combined work is AGPL; network use triggers source disclosure.
Every verdict on this site comes from one reviewed dataset and one deterministic engine. Nothing is written by hand per page, so a correction to the data propagates everywhere at once. Conditional answers say what they depend on. None of it is legal advice.
Three steps to a verdict
Choose the components
Pick any number of licenses from the dataset, from Unlicense to AGPL-3.0-or-later.
Choose how you distribute
The distribution model can change the verdict, not only the obligations.
- Internal use only (never distributed)
- Proprietary software you distribute as a binary
- Public SaaS / hosted web service
- You redistribute as open source
- Static linking
- Dynamic linking
Read the verdict and the obligations
Yes, no or it depends, with the note, the resulting work's license and a checklist of what you owe.
Compatible.
MIT, Apache-2.0, GPL-3.0-only combine into a GPL-3.0-only work.
General guidance, not legal advice.
Popular checks
Full matrix →Is Apache-2.0 compatible with GPL-2.0-only?
No. Apache-2.0's patent-termination and additional-restriction terms conflict with GPLv2. The single most-searched incompatibility.
Is MIT compatible with GPL-3.0-only?
Yes. Permissive code can be pulled into a GPL work; the combined distributed work becomes GPL. One-way: you cannot pull GPL back into a permissive project and keep it permissive.
Is GPL-2.0-only compatible with GPL-3.0-only?
No. Different copyleft versions with no upgrade clause cannot be merged. Resolve by finding a 'GPL-2.0-or-later' variant of the dependency.
Is Apache-2.0 compatible with GPL-3.0-only?
Yes. GPLv3 was written to accept Apache-2.0's patent terms. Combined work is GPLv3.
Is Apache-2.0 compatible with GPL-2.0-or-later?
It depends. Incompatible as GPLv2, but the 'or later' clause lets you upgrade the combined work to GPLv3, under which Apache-2.0 IS compatible.
Is MIT compatible with Apache-2.0?
Yes. Combine freely; retain all notices. Result can be relicensed (kept proprietary) downstream.
Is MPL-2.0 compatible with GPL-3.0-only?
Yes. Secondary-license mechanism covers GPLv3.
Is LGPL-2.1 compatible with GPL-2.0-only?
Yes. LGPL-2.1 can be relicensed up to GPLv2.