Skip to content

Reject OCI artifact attachments before image filesystem interpretation - #5

Merged
CompleteDotTech merged 2 commits into
mainfrom
fix/audit-2-artifact-semantics
Oct 26, 2026
Merged

CompleteDotTech merged 2 commits into
mainfrom
fix/audit-2-artifact-semantics

Conversation

@CompleteDotTech

Copy link
Copy Markdown
Contributor

Fixes #2

A correctly hashed OCI attestation attachment could previously be reported as a complete container filesystem and supply package metadata. Gate filesystem interpretation on explicit supported manifest/index and image-config media types, reject artifact intent and inconsistent manifest media types, and preserve verified manifest identity with an incomplete reason. Valid image siblings retain their observations; failed artifacts cannot supply consumer records.

Validation: reproduced eight unsupported/artifact/type cases against the old planner; 20 synthetic local-only tests pass, including isolated artifacts, both sibling orders, canonical identities, consumer exclusion and exploitability=not_tested. CLI help and git diff --check pass. Updated README and standalone SHA256SUMS. No images executed, registry access, target scans or production changes. Hosted Copilot review and exact-head six-platform/Python matrix are required before merge.

@CompleteDotTech
CompleteDotTech merged commit 8622b50 into main Oct 26, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[P2] Keep OCI artifact attachments out of container image inventories

1 participant