Repository navigation
Reject incomplete evidence and verify the installed package - #1
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
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.
A run could be approved even when its contract silently discarded checks or an output path was a directory. This release rejects malformed or empty contracts, duplicate fields, contradictory thresholds, directory artifacts, and inconsistent status packets. It also fixes CLI compatibility on Python 3.12–3.14.
The README now leads with a runnable missing-export demonstration. The 0.2.0 changelog documents stricter validation and migration steps. CI verifies tests, lint, formatting, builds, and an installed wheel outside the checkout across Python 3.11–3.14.
Validation: 62 tests passed with deprecations treated as errors; lint and formatting passed; sdist/wheel built; isolated installed-wheel init-example, validate, packet, and failure-to-pass demo passed. Checks establish configured evidence-contract compliance; CSV checks inspect headers, and metrics truthfulness remains outside the tool's scope.