Open-source licences, explained

The common open-source licences in plain words: what MIT, Apache-2.0, GPL, LGPL, MPL and AGPL allow and require when you ship an app or run a SaaS. Not legal advice.

MIT

Permissive

MIT is a short permissive licence: you can use, change and sell the code, closed source included, as long as you keep the copyright and licence notice.

Apache-2.0

Permissive

Apache-2.0 is a permissive licence with an explicit patent grant: you can use the code in any product, closed source included, if you keep its notices and say what you changed.

BSD-3-Clause

Permissive

BSD-3-Clause is a permissive licence: use the code anywhere, closed source included, keep the notice, and do not use the authors' names to promote your product. BSD-2-Clause is the same without the last condition.

ISC

Permissive

ISC is a very short permissive licence, equivalent in practice to MIT: use the code anywhere and keep the notice. 0BSD drops the notice requirement too.

Unlicense

Public domain

The Unlicense and CC0 dedicate the work to the public domain, with a fallback licence where that is not possible: use it for anything, with no conditions.

MPL-2.0

Weak copyleft

MPL-2.0 is a file-level copyleft: you can combine MPL code with closed-source code, but changes to the MPL files themselves must be shared under the MPL.

LGPL-2.1-only

Weak copyleft

LGPL-2.1 lets you use a library from closed-source software, provided users can replace the library with a modified version; changes to the library itself must stay under the LGPL.

LGPL-3.0-only

Weak copyleft

LGPL-3.0 is GPL-3.0 with extra permissions: closed-source software may use the library, provided users can replace it and changes to the library itself stay under the LGPL.

GPL-2.0-only

Strong copyleft

GPL-2.0 is a strong copyleft: if you distribute software that includes or links GPL-2.0 code, the whole program must be distributed under GPL-2.0, with its source code.

GPL-3.0-only

Strong copyleft

GPL-3.0 is a strong copyleft: if you distribute software that includes or links GPL-3.0 code, the whole program must be offered under GPL-3.0 with its source, and users must be able to install modified versions.

AGPL-3.0-only

Network copyleft

AGPL-3.0 is GPL-3.0 plus a network clause: if users interact with a modified version over a network, you must offer them its complete source code. It is the licence to check first in a hosted service.

EPL-2.0

Weak copyleft

EPL-2.0 is a weak copyleft at module level: you can combine EPL code with closed-source modules, but changes to the EPL code must be shared under the EPL.

EUPL-1.2

Strong copyleft

EUPL-1.2 is a copyleft licence written by the European Commission, valid in all EU languages. Distributed or communicated derivative works must stay under the EUPL or a listed compatible licence.

SSPL-1.0

Source-available (not open source)

SSPL is a source-available licence, not approved as open source. If you offer the software as a service, you must publish the source of the whole service stack used to run it.

BUSL-1.1

Source-available (not open source)

BUSL is a source-available licence: production use is restricted by an "Additional Use Grant" chosen by each publisher, and each version becomes open source (often Apache-2.0 or GPL) after a change date.

The families

FamilyWhat it asks of youExamples
Public domainThe author gave up their rights as far as the law allows: no conditions to follow.Unlicense, CC0-1.0
PermissiveYou can use, change and ship the code in any product, including closed-source ones. You must keep the copyright and licence notice (usually in a third-party notices file); Apache-2.0 also asks you to state changes and keep its NOTICE file.MIT, MIT-0, Apache-2.0, BSD-2-Clause, BSD-3-Clause
Weak copyleftYou can use the library in a closed-source product, but changes to the library's own files (MPL, EPL) or to the library itself (LGPL) must be shared under the same licence. LGPL also expects users to be able to replace the library, which is simple with dynamic linking and harder with static linking or bundling.LGPL-2.0-only, LGPL-2.1-only, LGPL-3.0-only, MPL-1.1, MPL-2.0
Strong copyleftIf you distribute software that includes or links this code (an installer, a mobile or desktop app, a container image you hand out, JavaScript sent to browsers), the whole combined work must be offered under the same licence, with its source code. Running it only on your own servers is not distribution.GPL-2.0-only, GPL-3.0-only, EUPL-1.1, EUPL-1.2, CECILL-2.1
Network copyleftLike strong copyleft, and more: if users interact with a modified version over a network (a SaaS or a web API), you must offer them its source code. The common case to check is AGPL in a hosted service.AGPL-3.0-only, OSL-3.0
Source-available (not open source)Not an open-source licence: the source is public but use is restricted, typically to stop you offering the software as a hosted service or competing with its publisher. Read the terms before using it in a product.SSPL-1.0, BUSL-1.1, Elastic-2.0, PolyForm-Noncommercial-1.0.0, PolyForm-Small-Business-1.0.0

Check your dependencies' licences