-
Notifications
You must be signed in to change notification settings - Fork 587
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
LicenseDeclared not as per SPDX License List #3030
Comments
The prefix
Is there anything I'm missing? |
Thanks to pointing me to this. I did check the
For other licenses that didn't resolve to a known SPDX License ID, this information was already extracted. Do you know why it failed to add extractionInfo for this? |
@aniketdn -- I can't say why this entry wasn't added. Is there a public image or other reproduction steps you could share to get an SBOM in this state? |
Unfortunately I do not have a public image I can point you to. |
@kzantow when i run a rpm query on the package on the Could it be the case that the license value that is obtained for |
Hi @kzantow and @aniketdn I think I've found minimal repro steps that use only public images and data: FROM fedora:42
RUN yum install -y libbsd obtaining SBOM: docker build -t test-syft-3030 .
syft -o spdx-json=spdx.json test-syft-3030 Filtered spdx-json, obtained by running {
"name": "libbsd",
"SPDXID": "SPDXRef-Package-rpm-libbsd-26e6215123b65c52",
"versionInfo": "0.12.2-4.fc41",
"supplier": "Organization: Fedora Project",
"originator": "Organization: Fedora Project",
"downloadLocation": "NOASSERTION",
"filesAnalyzed": true,
"packageVerificationCode": {
"packageVerificationCodeValue": "e82748ac35a0f41140355ab271c11a058fb7fa58"
},
"sourceInfo": "acquired package info from RPM DB: /usr/lib/sysimage/rpm/rpmdb.sqlite",
"licenseConcluded": "NOASSERTION",
"licenseDeclared": "(Beerware AND BSD-2-Clause AND BSD-3-Clause AND ISC AND libutil-David-Nugent AND MIT AND LicenseRef-Fedora-Public-Domain)",
"copyrightText": "NOASSERTION",
"externalRefs": [
{
"referenceCategory": "SECURITY",
"referenceType": "cpe23Type",
"referenceLocator": "cpe:2.3:a:fedoraproject:libbsd:0.12.2-4.fc41:*:*:*:*:*:*:*"
},
{
"referenceCategory": "SECURITY",
"referenceType": "cpe23Type",
"referenceLocator": "cpe:2.3:a:libbsd:libbsd:0.12.2-4.fc41:*:*:*:*:*:*:*"
},
{
"referenceCategory": "PACKAGE-MANAGER",
"referenceType": "purl",
"referenceLocator": "pkg:rpm/fedora/libbsd@0.12.2-4.fc41?arch=aarch64&upstream=libbsd-0.12.2-4.fc41.src.rpm&distro=fedora-42"
}
]
} Note that the |
Yes @willmurphyscode you are absolutely right! These steps reproduce the issue. |
What happened:
For the following package, the licenseDeclared is not as per the SPDX license list https://spdx.org/licenses/
The value
LicenseRef-Fedora-Public-Domain
does not match any of the SPDX identifiers listed.This value is causing the
ntia-checker
to generate a ValidationMessageUnrecognized license reference: LicenseRef-Fedora-Public-Domain
.What you expected to happen:
licenseDeclared field to have license values as per SPDX identifiers list.
If its a valid license, it can also be submitted to SPDX for its consideration as per: https://github.com/spdx/license-list-XML/blob/main/CONTRIBUTING.md
Steps to reproduce the issue:
Anything else we need to know?:
Environment:
syft version
: syft 1.9.0cat /etc/os-release
or similar): Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10 PST 2023; root:xnu-10002.61.3~2/RELEASE_X86_64 x86_64The text was updated successfully, but these errors were encountered: