Harden native release supply chain - #21
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.
Hardens AccordLock's native Windows and macOS release boundary with exact dependency profiling, target-native RustSec audits, ephemeral Cargo release targets, canonical staging, pinned support-file hashes, source identity revalidation, and adversarial packaging tests. Local validation passes source provenance, publication hygiene, the 81-theorem Lean source policy, the upstream modification inventory, the exact Windows dependency graph, and the packaging test suite. This PR does not claim production readiness: signed-install verification on clean machines, native macOS notarization, live infrastructure validation, and independent security review remain explicit external release gates.