Replies: 3 comments 1 reply
-
Hello @klasvo Unfortunately, Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
-
Close this as duplicate of #7189 |
Beta Was this translation helpful? Give feedback.
-
Hello @DmitriyLewen, I tested the changes in #7131, however, there are still invalid licenses in the SPDX json:
According to the SPDX specification, unknown licenses have to be defined: Cheers |
Beta Was this translation helpful? Give feedback.
-
Description
Hi, I noticed that the SPDX output of Trivy does not adhere to the specification. It includes license identifiers that are not on the SPDX license list.
For example, I scanned the image
registry.access.redhat.com/ubi9/ubi-minimal:9.4
and for packageaudit-libs
the license is listed asLGPLv2
which is not a valid license for SPDX. It should beLGPL-2.0-or-later
, I guess.I found issue #3267 that was closed/resolved in Mar 2023 that should have fixed it. But maybe there was a regression.
The complete list of invalid licenses in the SBOM of the scan is as follows:
Cheers
Volker
Desired Behavior
The SBOM contains valid license references:
Actual Behavior
The SBOM contains invalid license references:
Reproduction Steps
Target
Container Image
Scanner
License
Output Format
SPDX
Mode
Standalone
Debug Output
Operating System
Kubernetes
Version
Checklist
trivy clean --all
Beta Was this translation helpful? Give feedback.
All reactions