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
Is your feature request related to a problem? Please describe.
We use Black Duck for license and vulnerability scanning. I can upload a vcpkg-generated SBOM there, but it does not find any match. I am told, this is because vcpkgs SBOM are missing a purl element.
We have also contacted Synopsis. Maybe they can do something to support vcpkgs SBOMS without purl.
This suggestion (#30461) might also work, but I am not sure.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Add a package URL to generated SBOM files so that vulnerability
databases can start linking CVEs to vcpkg port versions.
Fixesmicrosoft/vcpkg#39254.
See also package-url/purl-spec#217 that has
not been resolved yet but should be resolved before this commit is
merged.
Is your feature request related to a problem? Please describe.
We use Black Duck for license and vulnerability scanning. I can upload a vcpkg-generated SBOM there, but it does not find any match. I am told, this is because vcpkgs SBOM are missing a purl element.
Proposed solution
Finish up this ongoing purl definition #32732 (or package-url/purl-spec#245) then add it to the generated SBOMs.
Describe alternatives you've considered
We have also contacted Synopsis. Maybe they can do something to support vcpkgs SBOMS without purl.
This suggestion (#30461) might also work, but I am not sure.
Additional context
No response
The text was updated successfully, but these errors were encountered: