OSLC Handbook Licenses
Please review OSLC Documentation for a primer on this, and the Licenses article for more details on softwre licensing.
BSD Zero Clause License
SPDX License ID
0BSD
Notes
This is a blanket license with no conditions.
Other Terms
| Description |
|---|
This license places no conditions whatsoever on using, copying, modifying or distributing the software for any purpose. |
GNU Affero General Public License 3.0
SPDX License IDs
AGPL-3.0-only
AGPL-3.0-or-later
Notes
AGPL-3.0 is the same license as GPL-3.0, but with an additional term in
section 13 which imposes a requirement for a modified version accessed
via remote computer network. AGPL-3.0 provides the option to use either
that version of the license only or to make it available under any later
version of that license. This is denoted in the standard license header
and by using AGPL-3.0-only or AGPL-3.0-or-later.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | It must be an actual copy of the license not a website link |
Retain notices on all files | X | X | X | X | Source files usually have a standard license header that includes a copyright notice and disclaimer of warranty. This is also where you determine if the license is “or later” or the specific version only |
Notice of modifications | X | X | Modified files must have “prominent notices that you changed the files” and a date | ||
Modifications or derivative work must be licensed under same license | X | X | Strong copyleft or reciprocal, project-based license meaning that derivative works must also be under AGPL-3.0. For more information about AGPL-3.0 compliance and this condition in particular (which is the same as for GPL-3.0), see the references provided or consult with your open source legal counsel. | ||
Provide corresponding source code | X | X | Corresponding Source = all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. Options for providing source = with binary, written offer, or via a network server. See section 6 for more details. For more information about AGPL-3.0 compliance and this condition in particular, see the references provided or consult your open source legal counsel. | ||
No additional restrictions | X | X | X | X | You may not impose any further restrictions on the exercise of the rights granted under this license. |
Termination Provisions
| Description |
|---|
License automatically terminates if you do not comply with the terms of the license |
License terminates if you initiate litigation claiming use of the program under this license violates a patent |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license or that version only, as specified. If no license version is specificed, then you may use any version ever published by the FSF. |
Other Terms
| Description | Compliance Notes |
|---|---|
Provide information necessary to install modified versions on User Products | If convey object code in, with, or specificially for use in a User Product and the right of possession for the User Product is tranferred as part of the conveyance, then the corresponding source code must include Installation Information (methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source) (see section 6 for more details) |
Apache Software License 1.1
SPDX License ID
Apache-1.1
Notes
Apache-1.1 and Entessa are essentially the same license (as per SPDX
License List Matching Guidelines). Because the OSI approved them
separately, they are listed separately (here and on the SPDX License
List).
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Acknowledgement must be included in end-user documentation, in software or wherever third-party acknowledgments appear | X | X | X | X | |
Name of project cannot be used for derived products without permission | X | X |
Apache Software License 2.0
SPDX License ID
Apache-2.0
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | Does not specify format for providing copy of license |
Notice of modifications | X | X | Modified files must include "prominent notices" of the modifications | ||
Retain all notices | X | X | Copyright notices and other notices do not have to be reproduced for binary distribution |
Termination Provisions
| Description |
|---|
Any patent claims accusing the work by a licensee results in termination of all patent licenses to the licensee. |
Artistic License 1.0 (Perl)
SPDX License ID
Artistic-1.0-Perl
Notes
This is the Artistic License 1.0 found on the Perl site, which is
different (particularly, clauses 5, 6, 7 and 8) than the Artistic
License 1.0 w/clause 8 found on the OSI site. This license has specific
use cases and conditions that are difficult to summarize; please see
sections 5-8 and relevant definitions for more details.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Retain all notices | X | Copyright notices and other notices | |||
Notice of modifications | X | X | Modified files must have "prominent notice" in each file stating how the file was modified and when | ||
Provide access to modifications | X | X | Do at least one of the following: place modification in the public domain or otherwise make them freely available; OR rename non-standard executables; OR "make other distribution arrangements" with the copyright holder (see section 3 for more details). | ||
Access to source | X | X | Do at least one of the following: provide a Standard Version of the executables and library files; OR provide source for your modifications; OR give non-standard executables non-standard name and document the differences with instructions on where to get the Standard Version; OR "make other distribution arrangements" with the copyright holder (see section 4 for more details) | ||
You may distribute this package as part of a larger (commercial) distribution, but cannot charge a fee for the standalone package. You may charge a reasonable fee for copying or support. | X | X | X | X |
Other Terms
| Description |
|---|
The following are not considered part of the package or do not fall under copyright of this package and subject to the license: scripts and library files supplied as input to or produced as output from the program; C subroutines (or comparably compiled subroutines in other languages) supplied by you and linked into this Package in order to emulate subroutines and variables of the language defined by this package; aggregation of this package with other software where the package is embedded and the interfaces are not visible to the end user (see sections 6, 7, and 8 for more details) |
Artistic License 2.0
SPDX License ID
Artistic-2.0
Notes
This license has specific use cases and conditions that are difficult to
summarize; please see sections 4-9 and relevant definitions for more
details.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Retain all notices | X | X | Copyright notices and other notices | ||
Notice of modifications | X | X | Document how the modified version differs from the standard version | ||
Provide access to modified version | X | X | Do at least one of the following: make modified version available to copyright holder under same license; OR ensure modified version does not prevent user from installing or running standard version and use different name; OR allow any recipients of modified version to make source available to others under same license or a similarly free/open license (see section 4 for more details) | ||
Access to source | X | Provide complete instructions on how to get source for standard version; instructions must be kept current for your distribution | |||
You may distribute this package as part of a larger (commercial) distribution, but cannot charge a licensing fee for the standalone package. You may charge distributor fees or licensing fees for other components in the distribution. | X | X | X | X |
Termination Provisions
| Description |
|---|
Any patent claims accusing the work by a licensee results in termination of all licenses to the licensee |
Other Terms
| Description |
|---|
Modified or standard versions linked with other works; embedding the package in a larger work of your own; or stand-alone binary or bytecode versions of applications that include the package may be distributed without restriction provided the result does not expose a direct interface to the package. See sections 8 for more details. |
Works that merely extend or make use of the package do not cause the package to be a modified version, are not considered parts of the package itself, and are not subject to the terms of this license. See section 9 for more details. |
BSD 2-Clause "Simplified" License
SPDX License ID
BSD-2-Clause
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
BSD 3-Clause "New" or "Revised" License
SPDX License ID
BSD-3-Clause
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
BSD-4-Clause (University of California-Specific)
SPDX License ID
BSD-4-Clause-UC
Notes
The advertising clause was rescinded by the University of California in
1999 for all material under BSD-4-Clause with University of California
copyright notice. Thus, you do not need to comply with the
advertising/acknowledgment requirement, which makes the license
essentially BSD-3-Clause.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
BSD 4-Clause "Original" or "Old" License
SPDX License ID
BSD-4-Clause
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Advertising materials "mentioning the features or use of this software" must include acknowledgment |
Boost Software License 1.0
SPDX License ID
BSL-1.0
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | For distributions “of machine-executable object code generated by a source language processor” (i.e., UB and MB use cases), these requirements need not be met. However, you might consider the need to identify the presence of software under BSL-1.0 for other reasons, especially if you have an agreement that wraps around this code/license. |
Common Development and Distribution License 1.0
SPDX License ID
CDDL-1.0
Notes
Versions 1.0 and 1.1 are essentially the same, except v1.1 adds a patent
infringement clause and choice of law.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | |||
Provide source code | X | X | X | You must inform recipients of how they can obtain source code “in a reasonable manner on or through a medium customarily used for software exchange”, including your modifications, if any | |
Notice of modifications | X | X | Provide notice of your modifications that identifies you as the contributor of the modification | ||
Modifications under same license | X | X | File-level reciprocal license meaning that modifications to any file or new files that contain part of original software are governed by the terms of this license. Larger works may be created by combining covered software with code not governed by this license, so long as you comply with this license for the covered software (see sections 1.6, 1.9, and 3.6 for more information) | ||
No additional restrictions | X | X | You may not impose any terms on source code that alters or restricts recipient’s rights under this license |
Termination Provisions
| Description |
|---|
License terminates upon failure to comply with license after a 30 day cure period |
Any patent claims accusing the software by a licensee results in termination of patent licenses to the licensee, with a 60 day cure (see section 6.2 for more details) |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of of same version or any later version of the license, unless the version you received states otherwise. |
Other Terms
| Description |
|---|
You may offer and charge a fee for warranty, support, indemnity or liability obligations to recipients. However, you must make it clear that any such offer is offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make. See section 3.4 for more details. |
You may distribute binary versions under a different license, so long as you do not limit or alter the recipient’s right in the source code under this license. You must make it clear that any differing terms are offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make (see section 3.6 for more details). |
Common Development and Distribution License 1.1
SPDX License ID
CDDL-1.1
Notes
Versions 1.0 and 1.1 are essentially the same, except v1.1 adds a patent
infringement clause and choice of law.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | |||
Provide source code | X | X | X | You must inform recipients of how they can obtain source code “in a reasonable manner on or through a medium customarily used for software exchange”, including your modifications, if any | |
Notice of modifications | X | X | Provide notice of your modifications that identifies you as the contributor of the modification | ||
Modifications under same license | X | X | File-level reciprocal license meaning that modifications to any file or new files that contain part of original software are governed by the terms of this license. Larger works may be created by combining covered software with code not governed by this license, so long as you comply with this license for the covered software (see sections 1.6, 1.9, and 3.6 for more details) | ||
No additional restrictions | X | X | You may not impose any terms on source code that alters or restricts recipient’s rights under this license |
Termination Provisions
| Description |
|---|
License terminates upon failure to comply with license after a 30 day cure period |
Any patent claims accusing the software by a licensee results in termination of patent licenses to the licensee, with a 60 day cure. If such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such parties in this license shall be taken into account in determining the amount or value of any payment or license (see section 6.2 and 6.3 for more details). |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license, unless the version you received states otherwise. |
Other Terms
| Description |
|---|
You may offer and charge a fee for warranty, support, indemnity or liability obligations to recipients. However, you must make it clear that any such offer is offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make (see section 3.4 for more details) |
You may distribute binary versions under a different license, so long as you do not limit or alter the recipient’s right in the source code under this license. You must make it clear that any differing terms are offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make (see section 3.6 for more details) |
Entessa Public License 1.0
SPDX License ID
Entessa
Notes
Apache-1.1 and Entessa are essentially the same license (as per SPDX
License List Matching Guidelines). Because the OSI approved them
separately, they are listed separately (here and on the SPDX License
List).
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Acknowledgement must be included in end-user documentation, in software or wherever third-party acknowledgments appear | X | X | X | X | |
Name of project cannot be used for derived products without permission | X | X |
Eclipse Public License 1.0
SPDX License ID
EPL-1.0
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | A copy of the license must be included with each copy of the program. While there is no explicit language requiring a copy of the license for a binary distribution, one would need to identify this license to meet other requirements, thus some reference to the license is practically necessary. | ||
Retain notices | X | X | You must retain license notices with every source code distribution or include notices in another likely location | ||
Provide source code | X | X | Must inform recipients how to obtain source code by reasonable manner via a "medium customarily used for software exchange" | ||
Notice of contributions | X | X | Include a note that identifies contributor as the originator of its contribution | ||
Modifications under same license | X | File-level reciprocal license meaning that modifications to any file or new files that contain part of original software are governed by the terms of this license. This does not include additional separate software modules that are distributed with the program and are not derivative works of the program (see sections 1 and 3 for more details) |
Termination Provisions
| Description |
|---|
License terminates upon failure to comply with "material terms or conditions" and failure to cure in a reasonable period of time after becoming aware of noncompliance |
Any patent claims accusing the software by a licensee results in termination of patent licenses to the licensee |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license. |
Other Terms
| Description |
|---|
You may distribute binary versions under a different license, provided you disclaim contributors from warranties, liability, and defend contributors against any third party claims brought as a result of your distribution. Clarify that any provisions offered by you are offered by you only (see section 3 and 4 for details) |
Eclipse Public License 2.0
SPDX License ID
EPL-2.0
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide license | X | X | X | Accompany the program with a statement that the source code if available under the license. For source code distributions, must provide a copy of the license. | |
Provide source code | X | X | Must inform recipients how to obtain source code by reasonable manner via a "medium customarily used for software exchange" | ||
Modifications under same license | X | File-level reciprocal license meaning that modifications to any file or new files that contain part of original software are governed by the terms of this license. This does not include additional separate software modules that are distributed with the program and are not derivative works of the program (see sections 1 and 3.2 for more details) | |||
Retain notices | X | X | X | X | You must retain license notices with every source code distribution or include notices in another likely location |
Termination Provisions
| Description |
|---|
License terminates upon failure to comply with "material terms or conditions" and failure to cure in a reasonable period of time after becoming aware of noncompliance |
Any patent claims accusing the software by a licensee results in termination of patent licenses to the licensee |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license. |
Other Terms
| Description |
|---|
You may distribute program under a different license, provided you disclaim contributors from warranties, liability, and defend contributors against any third party claims brought as a result of your distribution. Clarify that any provisions offered by you are offered by you only (see section 3 for details) |
You may distribute under an enumerated Secondary License if authorized by the initial Contributor or combined with code under that Secondary License (see section 3.2 for more details) |
GNU General Public License 2.0
SPDX License IDs
GPL-2.0-only
GPL-2.0-or-later
Notes
GPL-2.0 provides the option to use either that version of the license
only or to make it available under any later version of that license.
This is denoted in the standard license header and by using GPL-2.0-only
or GPL-2.0-or-later
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | It must be an actual copy of the license not a website link |
Retain notices on all files | X | X | X | X | Source files usually have a standard license header that includes a copyright notice and disclaimer of warranty. This is also where projects typically indicate if the -or-later version option is available. |
Notice of modifications | X | X | Modified files must have “prominent notices that you changed the files” and a date | ||
Modifications or derivative work must be licensed under same license | X | X | Strong copyleft or reciprocal, project-based license meaning that derivative works must also be under GPL-2.0. For more information about GPL-2.0 compliance and this condition in particular, see the references provided or consult your open source legal counsel. | ||
Provide corresponding source code | X | X | Corresponding Source = all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. Options for providing source = with binary, written offer (see section 3 for more details). For more information about GPL-2.0 compliance and this condition in particular, see the references provided or consult your open source legal counsel. | ||
No additional restrictions | X | X | X | X | You may not impose any further restrictions on the exercise of the rights granted under this license. |
Termination Provisions
| Description |
|---|
License automatically terminates if you do not comply with the terms of the license |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license or that version only, as specified. If no license version is specified, then you may use any version ever published by the FSF. |
GNU General Public License 3.0
SPDX License IDs
GPL-3.0-only
GPL-3.0-or-later
Notes
GPL-3.0 provides the option to use either that version of the license
only or to make it available under any later version of that license.
This is denoted in the standard license header and by using GPL-3.0-only
or GPL-3.0-or-later. For a comparison of GPL-3.0 to GPL-2.0, see
Copyleft Guide: Understanding GPLv3 As An Upgraded
GPLv2
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | It must be an actual copy of the license not a website link |
Retain notices on all files | X | X | X | X | Source files usually have a standard license header that includes a copyright notice and disclaimer of warranty. This is also were you determine if the license is “or later” or the specific version only |
Notice of modifications | X | X | Modified files must have “prominent notices that you changed the files” and a date | ||
Modifications or derivative work must be licensed under same license | X | X | Strong copyleft or reciprocal, project-based license meaning that derivative works must also be under GPL-3.0. For more information about GPL-3.0 compliance and this condition in particular, see the references provided or consult with your open source legal counsel. | ||
Provide corresponding source code | X | X | Corresponding Source = all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. Options for providing source = with binary, written offer, or via a network server (see section 6 for more details). For more information about GPL-3.0 compliance and this condition in particular, see the references provided or consult your open source legal counsel. | ||
May not prohibit circumvention of technological measures that prevent users from exercising rights under the license (see section 3 for more details) | X | X | X | X | |
No additional restrictions | X | X | X | X | You may not impose any further restrictions on the exercise of the rights granted under this license. |
Termination Provisions
| Description |
|---|
License automatically terminates if you do not comply with the terms of the license |
License terminates if you initiate litigation claiming use of the program under this license violates a patent |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license or that version only, as specified. If no license version is specificed, then you may use any version ever published by the FSF. |
Other Terms
| Description | Compliance Notes |
|---|---|
Author may include additional permissions making exceptions from license terms. You may remove additional permission when you convey the work. | Contributors may add certain additional restrictions for their contributions, including disclaimers, legal notices, limitation of trademark and publicity rights, extension of indemnification received by licensor. |
Provide information necessary to install modified versions on User Products | If convey object code in, with, or specificially for use in a User Product and the right of possession for the User Product is tranferred as part of the conveyance, then the corresponding source code must include Installation Information (methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source) (see section 6 for more details) |
ISC License
SPDX License ID
ISC
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | This information must appear "in all copies" |
Provide copyright notice | X | X | X | X | This information must appear "in all copies" |
GNU Library General Public License 2.0
SPDX License IDs
LGPL-2.0-only
LGPL-2.0-or-later
Notes
LGPL-2.0 and LGPL-2.1 are the same substantive license except for the
addition of section 6(b) in LGPL-2.1.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | It must be an actual copy of the license not a website link |
Retain notices on all files | X | X | X | X | Source files usually have a standard license header that includes a copyright notice and disclaimer of warranty. This is also were you determine if the license is “or later” or the specific version only |
Notice of modifications | X | X | Modified files must have “prominent notices that you changed the files” and a date | ||
Modifications or derivative work must be licensed under same license | X | X | Derivative works of the library must also be under LGPL (this usually includes statically linked code). | ||
Provide corresponding source code | X | X | complete source code = all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library (see section 4 or section 6, as applicable). | ||
No additional restrictions | X | X | X | X | You may not impose any further restrictions on the exercise of the rights granted under this license. |
Termination Provisions
| Description |
|---|
License automatically terminates if you do not comply with the terms of the license |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license or that version only, as specified. If no license version is specificed, then you may use any version ever published by the FSF. |
Other Terms
| Description | Compliance Notes |
|---|---|
Allows dynamic linking of code with “a work that uses the Library” under a different license, under certain conditions. | Terms of the other license must permit reverse engineering and debugging; must provide a copy of the license and prominent notice that the Library is used; must provide source code via one of the options in section 6 of the license. Also must include any data and utility programs needed for reproducing the executable, but this need not include anything that is normally distributed with the major components of the operating system. For more information about LGPL-2.0 compliance and this condition in particular, see the references provided or consult your open source legal counsel. |
GNU Lesser General Public License 2.1
SPDX License IDs
LGPL-2.1-only
LGPL-2.1-or-later
Notes
LGPL-2.0 and LGPL-2.1 are the same substantive license except for the
addition of section 6(b) in LGPL-2.1.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | It must be an actual copy of the license not a website link |
Retain notices on all files | X | X | X | X | Source files usually have a standard license header that includes a copyright notice and disclaimer of warranty. This is also were you determine if the license is “or later” or the specific version only |
Notice of modifications | X | X | Modified files must have “prominent notices that you changed the files” and a date | ||
Modifications or derivative work must be licensed under same license | X | X | Derivative works of the library must also be under LGPL (this usually includes statically linked code). | ||
Provide corresponding source code | X | X | complete source code = all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library (see section 4 or section 6, as applicable). | ||
No additional restrictions | X | X | X | X | You may not impose any further restrictions on the exercise of the rights granted under this license. |
Termination Provisions
| Description |
|---|
License automatically terminates if you do not comply with the terms of the license |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license or that version only, as specified. If no license version is specificed, then you may use any version ever published by the FSF. |
Other Terms
| Description | Compliance Notes |
|---|---|
Allows dynamic linking of code with “a work that uses the Library” under a different license, under certain conditions. | Terms of the other license must permit reverse engineering and debugging; must provide a copy of the license and prominent notice that the Library is used; must provide source code via one of the options in section 6 of the license. Also must include any data and utility programs needed for reproducing the executable, but this need not include anything that is normally distributed with the major components of the operating system. For more information about LGPL-2.1 compliance and this condition in particular, see the references provided or consult your open source legal counsel. |
GNU Lesser General Public License 3.0
SPDX License IDs
LGPL-3.0-only
LGPL-3.0-or-later
Notes
LGPL-3.0 incorporates the terms of GPL-3.0 and supplements the parent
license with the terms listed here.
License Versioning
| Description |
|---|
Allows use of covered code under the terms of of same version or any later version of the license or that version only, as specified. If no license version is specificed, then you may use any version ever published by the FSF. |
Other Terms
| Description | Compliance Notes |
|---|---|
If you modify the library so that it does not function without data or function supplied by your application, the modified library can only be distributed under the terms of GPL-3.0. This restriction does not apply if the data or function is supplied as an argument. | Object code incorporating header file material from the library that is not limited to numerical parameters, data structure layouts and accessors or small macros, inline functions and templates of fewer than ten lines must include a prominent notice that the library is used, its use is covered by LGPL-3.0, and provide a copy of the license (see section 3 for more details) |
Allows distribution of combined LGPL-3.0 and other code under under a different license, under certain conditions. | Allows use of a "suitable shared library mechanism" (including dynamic linking) to combine the LGPL-3.0 code with non-LGPL-3.0 code, so long as the source code is provided to allow the user to recombine or relink the application with a modified version of the LGPL-3.0 library. This must include installation information as defined in GPL-3.0, if necessary to install and execute a modified version of the combined work (see sections 4d and 4e for more details). For more information about LGPL-3.0 compliance and this condition in particular, see the references provided or consult your open source legal counsel. |
libpng License
SPDX License ID
Libpng
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
notice of modifications | X | X | Modified verions must be "plainly marked as such" and not misrepresented as the original software | ||
Provide copyright notice | X | X | Copyright notices may not be removed or altered for any source distribution |
Other Terms
| Description |
|---|
The origin of the code must not be misrepresented |
CMU License
SPDX License ID
MIT-CMU
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, provide this information "in supporting documentation" |
Provide copyright notice | X | X | X | X | For binary distributions, provide this information "in supporting documentation" |
MIT License
SPDX License ID
MIT
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | This information "shall be included in all copies or substantial portions of the Software". Some people interpret MIT as not implicating these requirements for binary distribution (e.g., UB and MB), but this is not the prevailing view and best practice is to include it. |
Provide copyright notice | X | X | X | X | This information "shall be included in all copies or substantial portions of the Software".Some people interpret MIT as not implicating these requirements for binary distribution (e.g., UB and MB), but this is not the prevailing view and best practice is to include it. |
Mozilla Public License 1.0
SPDX License ID
MPL-1.0
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | You must include a copy of the license with every source code distribution | ||
Retain notices | X | X | You must retain license notices with every source code distribution or include notices in another likely location | ||
Provide source code | X | X | Provide source code on same media as binary or make available via other electronic distribution mechanism for 12 months after initial availability or at least 6 months after a subsequent version has been made available. See section 3.2 for more details. | ||
Notice of modifications | X | X | Document changes you made and date; include a prominent statement as to the origin of the original code. See section 3.3 for more details. | ||
Modifications under same license | X | X | File-level reciprocal license meaning that modifications to any file or new files that contain part of original software are governed by the terms of this license. Larger works may be created by combining covered software with code not governed by this license, so long as you comply with this license for the covered software (see sections 1.10 and 3.7 for more details) |
Termination Provisions
| Description |
|---|
License terminates upon failure to comply with license after a 30 day cure period |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of of same version or any later version of the license. |
Other Terms
| Description |
|---|
Provide notice in a file called "LEGAL" containing any third party intellectual property rights for particular functionality or code, including if your modifications are an application programming intereface and you own or control patents which are reasonably necessary to implement the API. See section 3.4 for more details. |
You may offer and charge a fee for warranty, support, indemnity or liability obligations to recipients. However, you must make it clear that any such offer is offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make. See section 3.5 for more details. |
You may distribute binary versions under a different license, so long as you do not limit or alter the recipient’s right in the source code under this license. You must make it clear that any differing terms are offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make. See section 3.6 for more details. |
If it is impossible for you to comply with any of the terms of this license due to statute or regulation then you must comply with the terms of this License to the maximum extent possible; and describe the compliance limitations and the code they affect and include such description in all distributions of the source code (see section 3.4 for more details) |
Mozilla Public License 1.1
SPDX License ID
MPL-1.1
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | You must include a copy of the license with every source code distribution | ||
Retain notices | X | X | You must retain license notices with every source code distribution or include notices in another likely location | ||
Provide source code | X | X | Provide source code on same media as binary or make available via other electronic distribution mechanism for 12 months after initial availability or at least 6 months after a subsequent version has been made available. See section 3.2 for more details. | ||
Notice of modifications | X | X | Document changes you made and date; include a prominent statement as to the origin of the original code. See section 3.3 for more details. | ||
Modifications under same license | X | X | File-level reciprocal license meaning that modifications to any file or new files that contain part of original software are governed by the terms of this license. Larger works may be created by combining covered software with code not governed by this license, so long as you comply with this license for the covered software (see sections 1.9 and 3.7 for more details) |
Termination Provisions
| Description |
|---|
License terminates upon failure to comply with license after a 30 day cure period |
Any patent claims accusing the software by a licensee results in termination of all licenses to the licensee, with a 60 day cure. Any patent claims by a licensee accusing any contributor results in termination of all of that contributor’s patent licenses (see section 8.2 and 8.3 for more details). |
If you initiate a patent infringement litigation against the initial developer or a contributor alleging that any software, hardware or device other than a contributor’s version infringed any patent, then the license from such parties terminates (see section 8.2 for more details). |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of of same version or any later version of the license. |
Other Terms
| Description |
|---|
Provide notice in a file called, LEGAL, of any third party intellectual property rights for particular functionality or code, including if your modifications are an application programming intereface and you own, control, or have knowledge of any patent licenses which are reasonably necessary to implement the API. See section 3.4 for more details. |
You may offer and charge a fee for warranty, support, indemnity or liability obligations to recipients. However, you must make it clear that any such offer is offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make. See section 3.5 for more details. |
You may distribute binary versions under a different license, so long as you do not limit or alter the recipient’s right in the source code under this license. You must make it clear that any differing terms are offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make. See section 3.6 for more details. |
You may distribute binary versions under a different license, so long as you do not limit or alter the recipient’s right in the source code under this license. You must make it clear that any differing terms are offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make. See section 3.6 for more details. |
Mozilla Public License 2.0
SPDX License ID
MPL-2.0
Notes
This license includes a license-compatibility provision related to use
of the code with the GPL-2.0-or-later, LGPL-2.1-or-later, and
GPL-3.0-or-later which is difficult to capture, please see sections
1.12, 2.4, 3.3, and 10.4 for more details.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide license | X | X | You must inform recipients that source code is goverened by this licenses and how to obtain a copy | ||
Modifications under same license | X | File-level reciprocal license meaning that modifications to any file or new files that contain part of original software are governed by the terms of this license. Larger works may be created by combining covered software with code not governed by this license, so long as you comply with this license for the covered software (see sections 1.10 and 3.3 for more details) | |||
Retain notices | X | X | You must retain license notices with every source code distribution or include notices in another likely location | ||
Provide source code | X | X | Must inform recipients how to obtain source code by reasonable means in a timely manner and at no cost more than the cost of distribution to the recipient. |
Termination Provisions
| Description |
|---|
License terminates upon failure to comply with license unless certain conditions are met by you and contributor (see section 5.1 for more details) |
Any patent claims accusing the software by a licensee results in termination of all licenses to the licensee |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license. |
Other Terms
| Description |
|---|
You may distribute binary versions under a different license, so long as you do not limit or alter the recipient’s right in the source code under this license. |
You may offer and charge a fee for warranty, support, indemnity or liability obligations to recipients. However, you must make it clear that any such offer is offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make. See section 3.5 for more details. |
You may distribute binary versions under a different license, so long as you do not limit or alter the recipient’s right in the source code under this license. You must make it clear that any differing terms are offered by you alone and you agree to indemnify the initial developer and every contributor for any liability incurred by them as a result of the offer you make. See section 3.6 for more details. |
Microsoft Public License
SPDX License ID
Ms-PL
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | Include a complete copy of license with source code distributions | ||
Retain all notices | X | X | X | X | Retain all notices present in software |
Source code under same license | X | X | Distributions of "any portion of the software in source code form" must be under this license | ||
Comply with this license | X | X | Object or compiled code distributions must be under a license that complies with this license |
Termination Provisions
| Description |
|---|
Any patent claims by licensee against any contributor accusing the software result in termination of all patent licenses from that contributor |
University of Illinois/NCSA Open Source License
SPDX License ID
NCSA
Notes
NCSA is essentially an MIT grant with BSD-3-Clause conditions, thus
compliance is the same as BSD-3-Clause.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
OpenSSL License
SPDX License ID
OpenSSL
Notes
This license is actually a set of two licenses, which have similar text
and requirements but different copyright holders and therefore different
acknowledgment text. Some requirements to include acknowledgements may
only apply if you are using that part of the project written by a
specific copyright holder.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Acknowledgement must be included for any redistribution | X | X | X | X | |
Include acknowledgement in advertising mentioning features or use | |||||
Include acknowledgement in advertising mentioning features or use. "The word cryptographic can be left out if the rouines from the library being used are not cryptographic related". | |||||
Include acknowledgement If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) | |||||
Name of project cannot be used for derived products without permission | X | X |
PHP License v3.0
SPDX License ID
PHP-3.0
Notes
PHP-3.0 and PHP-3.01 are the same license, but for a slight variation in
the acknowledment text.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Name of project cannot be used for derived products without permission | X | X | |||
Acknowlegment must be retained in all redistributions | X | X | X | X |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license. |
PHP License v3.01
SPDX License ID
PHP-3.01
Notes
PHP-3.0 and PHP-3.01 are the same license, but for a slight variation in
the acknowledment text.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Name of project cannot be used for derived products without permission | X | X | |||
Acknowlegment must be retained in all redistributions | X | X | X | X |
License Versioning
| Description |
|---|
Allows use of covered code under the terms of same version or any later version of the license. |
Plexus Classworlds License
SPDX License ID
Plexus
Notes
This license also includes a clause that states, "due credit should be
given" to the copyright holder, but given the non-obligatory nature of
"should", this is not considered a requirement.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Provide copyright notice | X | X | X | X | For binary distributions, this information must be provided in “the documentation and/or other materials provided with the distribution” |
Name of project cannot be used for derived products without permission | X | X |
Python License 2.0
SPDX License ID
Python-2.0
Notes
This is a license “stack” comprised of various licenses that apply to
Python as it has developed over the years.
Conditions
| Description | UB | MB | US | MS | Compliance Notes |
|---|---|---|---|---|---|
Provide copy of license | X | X | X | X | |
Provide copyright notice | X | X | X | X | |
Notice of modifications | X | X | Indicate the nature of the modifiations made in the work |
Termination Provisions
| Description |
|---|
Termination of license upon breach |
TCL/TK License
SPDX License ID
TCL
Other Terms
| Description |
|---|
Modified versions need not follow this license, provided that new license terms appear on first page of each applicable file |
zlib License
SPDX License ID
zlib
Other Terms
| Description |
|---|
This license also includes a request, but not a requirement for acknowledgment of use in your product documentation. |