License scanning of CycloneDX files (ULTIMATE ALL)
- Introduced in GitLab 15.9 for GitLab SaaS with two flags named
package_metadata_synchronization. Both flags are disabled by default and both flags must be enabled for this feature to work.
- Enabled in GitLab 15.10 for GitLab SaaS.
- Introduced in GitLab 15.10 for self-managed GitLab with two flags named
package_metadata_synchronization, both of which must be enabled for this feature to work. The flags are disabled by default due to the initial performance load when the license database is first imported. Work to improve performance is being tracked in issue 397670.
- Enabled in GitLab 15.11 for self-managed GitLab.
The legacy License Compliance analyzer was deprecated in GitLab 15.9 and removed in GitLab 16.3. To continue using GitLab for License Compliance, remove the License Compliance template from your CI/CD pipeline and add the Dependency Scanning template. The Dependency Scanning template is now capable of gathering the required license information so it is no longer necessary to run a separate License Compliance job. The License Compliance CI/CD template should not be removed prior to verifying that the
package_metadata_synchronization flags are enabled for the instance and that the instance has been upgraded to a version that supports the new method of license scanning. To begin using the Dependency Scanner quickly at scale, you may set up a scan execution policy at the group level to enforce the SBOM-based license scan for all projects in the group. Then, you may remove the inclusion of the
Jobs/License-Scanning.gitlab-ci.yml template from your CI/CD configuration. If you wish to continue using the legacy License Compliance feature, you can do so by setting the
LICENSE_MANAGEMENT_VERSION CI variable to
4. This variable can be set at the project, group or instance level. This configuration change will allow you to continue using an existing version of the License Compliance without having to adopt the new approach. Bugs and vulnerabilities in this legacy analyzer will no longer be fixed.
To detect the licenses in use, License Compliance relies on running the Dependency Scanning CI Jobs, and analyzing the CycloneDX Software Bill of Materials (SBOM) generated by those jobs. Other 3rd party scanners may also be used as long as they produce a CycloneDX file with a list of dependencies for one of our supported languages. This method of scanning is also capable of parsing and identifying over 500 different types of licenses, as defined in the SPDX list. Licenses not in the SPDX list are reported as "Unknown". License information can also be extracted from packages that are dual-licensed, or have multiple different licenses that apply.
Enable license scanning
- On GitLab self-managed only, enable Synchronization with the GitLab License Database in Admin Area for the GitLab instance. On GitLab SaaS this step has already been completed.
- Enable Dependency Scanning and ensure that its prerequisites are met.
.gitlab-ci.yml file, remove the deprecated line
Supported languages and package managers
License scanning is supported for the following languages and package managers:
The supported files and versions are the ones supported by Dependency Scanning.
GitLab has limited support for composite licenses.
License compliance can read multiple licenses, but always considers them combined using the
AND operator. For example,
if a dependency has two licenses, and one of them is allowed and the other is denied by the project policy,
GitLab evaluates the composite license as denied, as this is the safer option.
The ability to support other license expression operators (like
WITH) is tracked
in this epic.
Blocking merge requests based on detected licenses
Users can require approval for merge requests based on the licenses that are detected by configuring a license approval policy.
Running in an offline environment
For self-managed GitLab instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required to successfully scan CycloneDX reports for licenses. For more information, see the offline quick start guide.
A CycloneDX file is not being scanned and appears to provide no results
Ensure that the CycloneDX file adheres to the CycloneDX JSON specification. This specification does not permit duplicate entries. Projects that contain multiple SBOM files should either report each SBOM file up as individual CI report artifacts or they should ensure that duplicates are removed if the SBOMs are merged as part of the CI pipeline.
You can validate CycloneDX SBOM files against the
CycloneDX JSON specification as follows:
$ docker run -it --rm -v "$PWD:/my-cyclonedx-sboms" -w /my-cyclonedx-sboms cyclonedx/cyclonedx-cli:latest cyclonedx validate --input-version v1_4 --input-file gl-sbom-all.cdx.json Validating JSON BOM... BOM validated successfully.
If the JSON BOM fails validation, for example, because there are duplicate components:
Validation failed: Found duplicates at the following index pairs: "(A, B), (C, D)" #/properties/components/uniqueItems
This issue can be fixed by updating the CI template to use jq to remove the duplicate components from the
gl-sbom-*.cdx.json report by overriding the job definition that produces the duplicate components. For example, the following removes duplicate components from the
gl-sbom-gem-bundler.cdx.json report file produced by the
include: - template: Jobs/Dependency-Scanning.gitlab-ci.yml gemnasium-dependency_scanning: after_script: - apk update && apk add jq - jq '.components |= unique' gl-sbom-gem-bundler.cdx.json > tmp.json && mv tmp.json gl-sbom-gem-bundler.cdx.json