Look up ~25 common SPDX licenses (MIT, Apache-2.0, GPL-3.0-only, LGPL, BSD, MPL-2.0, AGPL, and more) to see their category, key obligations, and a plain-English summary; check whether two licenses are generally compatible and why — e.g. can a GPL-3.0 dependency be used in an MIT project.
No license selected
Choose an SPDX identifier above to see its category, obligations, and a plain-English summary.
License categories and obligations are hand-authored from publicly documented SPDX license texts and choosealicense.com/FSF-style summaries. The compatibility checker models a handful of well-known real-world rules (e.g. GPLv2-only vs GPLv3-only incompatibility, Apache-2.0 vs GPL-2.0-only, CDDL/EPL vs GPL) plus a simplified permissive/weak-copyleft/strong-copyleft/public-domain hierarchy for everything else — treat it as a starting point for a conversation with legal counsel, not a substitute for one.
Look up ~25 common SPDX licenses (MIT, Apache-2.0, GPL-3.0-only, LGPL, BSD, MPL-2.0, AGPL, and more) to see their category, key obligations, and a plain-English summary; check whether two licenses are generally compatible and why — e.g. can a GPL-3.0 dependency be used in an MIT project.
The Compatibility Check tab explains the direction and reasoning. Generally the combined work must be distributed under GPL terms.
Look it up in the License Lookup tab for its category, key obligations and a plain-English summary.
About 25 common SPDX licenses including MIT, Apache-2.0, GPL, LGPL, BSD, MPL-2.0 and AGPL.
No. Results are general guidance, so consult a lawyer for important licensing decisions.
No. This tool runs entirely in your browser — your input is processed locally on your device and is never uploaded or stored on a server.