You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an SBOM in CycloneDX format. It contains the field metadata.component.version. When I call Grype to analyse this SBOM and output the result as CycloneDX, every single field of the original SBOM is included in the resulting document, except for metadata.component.version. (Timestamp and serial number are different, of course)
What you expected to happen:
I would have expected for no field to vanish.
How to reproduce it (as minimally and precisely as possible):
If this is indeed a bug and not a design choice, I am willing to attempt to take care of it. I will need some pointers though, because I have no clue where to start.
What happened:
I have an SBOM in CycloneDX format. It contains the field metadata.component.version. When I call Grype to analyse this SBOM and output the result as CycloneDX, every single field of the original SBOM is included in the resulting document, except for metadata.component.version. (Timestamp and serial number are different, of course)
What you expected to happen:
I would have expected for no field to vanish.
How to reproduce it (as minimally and precisely as possible):
Go to your favourite repo.
Generate an SBOM with a component version:
(Use a formatter for nice JSON output to see that the field is present)
Scan for vulnerabilities:
The field is missing.
Anything else we need to know?:
If this is indeed a bug and not a design choice, I am willing to attempt to take care of it. I will need some pointers though, because I have no clue where to start.
Environment:
grype version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: