Skip to content
BENIBIX Learn

License Compatibility

Development🚀 Product & ReleasesSoftware Licenses

Also known as Compatible Licenses, License Conflict, GPL Compatibility

Can code with two sets of rules go in one app? This is the answer.

Think of it like

It is like mixing paints. Some mix well, and some make a mess you cannot undo.

Example

Jack wants to add an Apache 2.0 library to a GPL 2.0 only program. The two clash, so he picks a different library that uses the MIT license.

Why it matters

A clash can stop you from sharing your program at all. It is cheap to check before you add a library and costly to fix after.

Definition

License compatibility is whether code under two licenses can be joined in one program that you share. It works when you can obey both licenses at once. Code under a loose license can go into a GPL program, because the GPL's rules cover the loose ones. Two strong copyleft licenses often clash. Each one wants the whole program to use it.
Code moves easily from left to right on this line. Moving it the other way is where clashes start.

Common mistake

Thinking two open source licenses always mix. Apache 2.0 code fits into a GPL 3.0 program, but not into one that is GPL 2.0 only.

Key takeaways

  1. 1
    Obey both at once. They fit when one program can follow all the rules of each.
  2. 2
    Permissive mixes easily. MIT and BSD code can go into almost any program.
  3. 3
    Copyleft can clash. Two strong copyleft rules may each want the whole app.