Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(spdx): use hasExtractedLicensingInfos for licenses not in the SPDX license list #7721

Open
DmitriyLewen opened this issue Oct 14, 2024 Discussed in #7716 · 0 comments
Open

fix(spdx): use hasExtractedLicensingInfos for licenses not in the SPDX license list #7721

DmitriyLewen opened this issue Oct 14, 2024 Discussed in #7716 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. scan/license Issues relating to license scanning scan/sbom Issues relating to SBOM

Comments

@DmitriyLewen
Copy link
Contributor

Description

We can only use licenses from SPDX license list in licenseConcluded and licenseDeclared fields.
For other licenses, we should create new LicenseRef-* component (see hasExtractedLicensingInfos field - https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/#d46-license-expressions-in-rdf) and use this component in licenseConcluded and licenseDeclared
See more details here - #7716

Discussed in #7716
@DmitriyLewen DmitriyLewen added the kind/bug Categorizes issue or PR as related to a bug. label Oct 14, 2024
@DmitriyLewen DmitriyLewen changed the title fix(spdx): use fix(spdx): use hasExtractedLicensingInfos for licenses not in the SPDX license list Oct 14, 2024
@knqyf263 knqyf263 added scan/sbom Issues relating to SBOM scan/license Issues relating to license scanning labels Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. scan/license Issues relating to license scanning scan/sbom Issues relating to SBOM
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@knqyf263 @DmitriyLewen