-
-
Notifications
You must be signed in to change notification settings - Fork 64
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.
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
Merging vcpkg created sboms #377
Comments
I'm not sure if you can merge spdx files directly, might need to transform them to CycloneDx first. Are there maybe spdx merge tools, that would offer a more native solution? |
Oh, I see. Transform via cyclonedx convert, then merge. I will try. |
I did a similar a test with converted SBOMs but the result is the same (I guess, it converted implicitly):
|
@KUGA2 I think you get the best result if you convert explicitly and then do a flat merge (i.e. without --hierarchical). Merging does not support the spdx format; instead it tries to read it as a cyclonedx json, which is the reason why the result of the flat merge above was basically empty. For a hierarchical merge, you'd need have the metadata component available in the BOMs to be merged, which you don't have. |
This works: But my original use case, importing into Black Duck, still shows no component. Closing this here. |
Has anyone tried this?
vcpkg generates a SPDX file containing the SBOM information for each package that is installed. The files are located in <installed_dir>//share//vcpkg.spdx.json.
https://learn.microsoft.com/en-us/vcpkg/reference/software-bill-of-materials
I was hoping to use this to merge them. Sadly, it does not work.
Reproduction:
(i uploaded the jsons here for reproduction: inputs.zip )
(without hierarchical, it works but the result file is basically empty)
The text was updated successfully, but these errors were encountered: