(compliance/contracts): add approved licenses to custom allowlist#2452
Merged
migmartri merged 1 commit intochainloop-dev:mainfrom Oct 1, 2025
Merged
(compliance/contracts): add approved licenses to custom allowlist#2452migmartri merged 1 commit intochainloop-dev:mainfrom
migmartri merged 1 commit intochainloop-dev:mainfrom
Conversation
…cense.name) Signed-off-by: Victoria <kaysa.vps@gmail.com>
migmartri
approved these changes
Oct 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The sbom-banned-licenses policy correctly flagged unknown licenses in the SBOM. After reviewing and confirming that these are permitted licenses, it is safe to add them to the allowlist.
Fixes #2451
This PR adds Apache-2.0 as a permitted custom license (via the license.name field in the SBOM). While SPDX identifiers in the id or expression fields are the recommended approach for open source components, we’ve observed some cases where the license.name field is still used.