Replies: 2 comments 6 replies
-
Hello @wkoot These components were found from different lock files:
That is why we create 2 components for regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
6 replies
-
I would like to add that this is now also producing SBOM files that are no longer accepted by Dependency-Track
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
I obtain the following two components which only differ by their
bom-ref
, within a single scan.Only the first occurrence is listed in the bom dependencies, in both
ref
anddependsOn
fields.Not sure if (and if so, how) this is related to #7337, so opened as a separate discussion.
This scan and outputfile was produced with the docker image
aquasec/trivy:0.55.1
as follows:Component 1:
Component 2:
Desired Behavior
Components 1 and 2 should be deduplicated, only leaving a single component - to which the vulnerabilities and dependencies are linked.
Actual Behavior
Two duplicate components were produced, which only differ from each other in their
bom-ref
.Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Output Format
CycloneDX
Mode
Standalone
Debug Output
Operating System
Docker version 26.1.0, build 9714adc, Rocky Linux release 8.9 (Green Obsidian)
Version
# trivy --version Version: 0.55.1
Checklist
trivy clean --all
Beta Was this translation helpful? Give feedback.
All reactions