chore: add SCANOSS license curations (2 need review) - #28
Merged
Conversation
Auto-generated license curations for components detected by SCANOSS. Entries marked UNKNOWN need manual review — look up the upstream project license. Auto-generated — review before merging.
alaindargelas
approved these changes
Sep 2, 2026
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.
Auto-generated license curations from SCANOSS scan.
Resolved automatically: 0 components — no action needed
Needs manual review: 2 components (search for
UNKNOWN)What to do
Only entries with
"license": "UNKNOWN"need action. For each one:notefieldUNKNOWNwith the SPDX ID (e.g.MIT,Apache-2.0,GPL-2.0-only)"exclude": trueEntries with a license already set (e.g.
auto-known-projects) are resolved — no action needed.Once merged, the next ORT scan will pick up these curations automatically.