Repository navigation
Complete v0.1.0 SBOM attestation without replacing published bytes - #366
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The original v0.1.0 publisher pushed the immutable image and signed its provenance, then failed SBOM autodetection because the valid CycloneDX 1.6 document omits optional serialNumber. Use the supported explicit CycloneDX predicate mode for the normal publisher and a main-only completion workflow bound to the existing image digest, original producer/run/attempt, artifact ZIP, and unchanged SBOM SHA.
The completion verifies original required step outcomes, source/signer provenance and invocationId, all 13 component/archive identities, pinned official schemas, and anonymous full-output readback. It signs and verifies the original SBOM predicate without rebuilding or pushing an image; the original run remains failed. There are no subject/digest inputs or overwrite path.
Validation: 7 focused tests including wrong source/digest/run/attempt, prior step failure, truncated/unknown SBOM metadata and changed archives; actual retained API/ZIP/provenance response binding; official schema hook with 3 rejected controls; Python/YAML/Bash syntax and git diff --check. Native package suites and provider fixtures reuse their original PASS evidence.