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
Most of our images should now be including the SBOM as an attestation layer in the manifest. It would be great if the ci container used the existing SBOM from the image instead of running the syft container every time.
Some images don't include the SBOM so we would still need the syft container as a fallback.
Reason for change
Syft container is finicky and sometimes takes a very long time if the image is large and prone to timing out.
Proposed code change
Spad has all the details about how to check for existing SBOM and how to retrieve it.
The text was updated successfully, but these errors were encountered:
Is this a new feature request?
Wanted change
Most of our images should now be including the SBOM as an attestation layer in the manifest. It would be great if the ci container used the existing SBOM from the image instead of running the syft container every time.
Some images don't include the SBOM so we would still need the syft container as a fallback.
Reason for change
Syft container is finicky and sometimes takes a very long time if the image is large and prone to timing out.
Proposed code change
Spad has all the details about how to check for existing SBOM and how to retrieve it.
The text was updated successfully, but these errors were encountered: