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
Should this be Unsupported
either for SBOM?
#20346
Comments
The identify status is different due to the SBOM implementation is not same as Vulnerability.
|
fixes goharbor#20346 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
fixes goharbor#20346 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
fixes goharbor#20346 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
fixes goharbor#20346 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
artifact object's addition_links has sboms item when it support to generate sbom fixes goharbor#20346 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
artifact object's addition_links has sboms item when it support to generate sbom fixes goharbor#20346 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
artifact object's addition_links has sboms item when it support to generate sbom fixes goharbor#20346 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
artifact object's addition_links has sboms item when it support to generate sbom fixes #20346 Signed-off-by: stonezdj <stone.zhang@broadcom.com>
How can we help you?
The text was updated successfully, but these errors were encountered: