GitLab Licensing and Compatibility
GitLab CE is licensed under the terms of the MIT License. GitLab EE is licensed under "The GitLab Enterprise Edition (EE) license" wherein there are more restrictions. See their respective LICENSE files (CE, EE) for more information.
In order to comply with the terms the libraries we use are licensed under, we have to make sure to check new gems for compatible licenses whenever they're added. To automate this process, we use the license_finder gem by Pivotal. It runs every time a new commit is pushed and verifies that all gems in the bundle use a license that doesn't conflict with the licensing of either GitLab Community Edition or GitLab Enterprise Edition.
Some gems may not include their license information in their
gemspec file. These won't be detected by License Finder, and will have to be verified manually.
License Finder commands
There are a few basic commands License Finder provides that you'll need in order to manage license detection.
To verify that the checks are passing, and/or to see what dependencies are causing the checks to fail:
bundle exec license_finder
To whitelist a new license:
license_finder whitelist add MIT
To blacklist a new license:
license_finder blacklist add GPLv2
To tell License Finder about a dependency's license if it isn't auto-detected:
license_finder licenses add my_unknown_dependency MIT
For all of the above, please include
--why "Reason" and
--who "My Name" so the
decisions.yml file can keep track of when, why, and who approved of a dependency.
More detailed information on how the gem and its commands work is available in the License Finder README.
Libraries with the following licenses are acceptable for use:
- The MIT License (the MIT Expat License specifically): The MIT License requires that the license itself is included with all copies of the source. It is a permissive (non-copyleft) license as defined by the Open Source Initiative.
- LGPL (version 2, version 3): GPL constraints regarding modification and redistribution under the same license are not required of projects using an LGPL library, only upon modification of the LGPL-licensed library itself.
- Apache 2.0 License: A permissive license that also provides an express grant of patent rights from contributors to users.
- Ruby 1.8 License: Dual-licensed under either itself or the GPLv2, defer to the Ruby License itself. Acceptable because of point 3b: "You may distribute the software in object code or binary form, provided that you do at least ONE of the following: b) accompany the distribution with the machine-readable source of the software."
- Ruby 1.9 License: Dual-licensed under either itself or the BSD 2-Clause License, defer to BSD 2-Clause.
- BSD 2-Clause License: A permissive (non-copyleft) license as defined by the Open Source Initiative.
- BSD 3-Clause License (also known as New BSD or Modified BSD): A permissive (non-copyleft) license as defined by the Open Source Initiative
- ISC License (also known as the OpenBSD License): A permissive (non-copyleft) license as defined by the Open Source Initiative.
- Creative Commons Zero (CC0): A public domain dedication, recommended as a way to disclaim copyright on your work to the maximum extent possible.
- Unlicense: Another public domain dedication.
- OWFa 1.0: An open-source license and patent grant designed for specifications.
Libraries with the following licenses are unacceptable for use:
- GNU GPL (version 1, version 2, version 3, or any future versions): GPL-licensed libraries cannot be linked to from non-GPL projects.
- GNU AGPLv3: AGPL-licensed libraries cannot be linked to from non-GPL projects.
- Open Software License (OSL): is a copyleft license. In addition, the FSF recommend against its use.
- Facebook BSD + PATENTS: is a 3-clause BSD license with a patent grant that has been deemed Category X by the Apache foundation.
- WTFPL: is a public domain dedication rejected by the OSI (3.2). Also has a strong language which is not in accordance with our diversity policy.
Requesting Approval for Licenses
Libraries that are not listed in the Acceptable Licenses or Unacceptable Licenses list can be submitted to the legal team for review. Please email
firstname.lastname@example.org with the details. After a decision has been made, the original requestor is responsible for updating this document.
Decisions regarding the GNU GPL licenses are based on information provided by The GNU Project, as well as the Open Source Initiative, which both state that linking GPL libraries makes the program itself GPL.
If a gem uses a license which is not listed above, open an issue and ask. If a license is not included in the "acceptable" list, operate under the assumption that it is not acceptable.
Keep in mind that each license has its own restrictions (typically defined in their body text). Please make sure to comply with those restrictions at all times whenever an external library is used.
Gems which are included only in the "development" or "test" groups by Bundler are exempt from license requirements, as they're not distributed for use in production.
NOTE: This document is not legal advice, nor is it comprehensive. It should not be taken as such.