fix: bind release evidence to exact archive contents - #32
Merged
codeforester merged 1 commit intoSep 17, 2026
Conversation
codeforester
deleted the
bug/23-20260917-bug-bind-release-evidence-to-the-actual-archive-inventory
branch
September 17, 2026 16:43
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
1 participant
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.
Summary
Validate exact SPDX inventory, hashes, package relationships and source identities against the archive; bind structured provenance to subject and dependencies. Reject duplicate JSON keys and mismatched JSON types. Validate all archive paths/types before safe extraction. Default verification executes no payload code; --trusted-smoke is explicit opt-in. Retain offline vendor integrity checks and document consistency versus authenticity.
Validation
Full ./tests/validate.sh passed: 27 BATS cases, independent SPDX validation, cross-timezone reproducibility, standalone trusted smoke, and 22 coherent-checksum/unsafe-archive/execution-boundary regressions. Synthetic fixtures only.
Fixes #23