Repository navigation
Verify exact release source and add bounded security campaigns - #11
Draft
aksum-labs-publisher[bot] wants to merge 1 commit into
Draft
aksum-labs-publisher[bot] wants to merge 1 commit into
aksum-labs-publisher[bot] wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Release verification now binds the protected tag to accepted main source, current required check results, and hash-matched review evidence. Scheduled checks retain dated advisory results and synthetic fuzz findings, including a digest-pinned ClusterFuzzLite build.
Adds validated Security Insights metadata, a guarded optional PyPI route, supported installation evidence, and a synthetic terminal demo. Preserves the two-message scope and genuine review gates. Issues and Discussions remain disabled.
Validation: 169 local tests; formatting, typing, workflow and Security Insights validation; reviewed SHA-only secret-scan findings; a local 10,000-iteration ClusterFuzzLite campaign. Hosted results are tracked separately. This follows PR #7 without changing its review head.