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
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.
Community-health files, needed before the repo goes public, plus one metadata field for crates.io.
SECURITY.md— routes vulnerability reports to a private channel (GitHub advisories / signedemail), so a hash divergence or a validator bypass is never disclosed in a public issue. Spells out
what counts as a vulnerability here: a wrong hash, malformed input that gets hashed instead of
refused, a panic on untrusted input, an unsafe surface (only the opt-in
yamlfeature has one).CONTRIBUTING.md— this is the reference implementation, so it states the rule plainly: whenthe crate and the spec disagree, the spec wins. A hash-affecting change belongs in the protocol repo;
the conformance vectors are a mirror and are not edited here.
homepage = "https://ledvar.org"on the workspace and all three crates — the project linkcrates.io shows.
Docs and metadata only. No source, no behaviour, no hash affected — the three crates build
byte-identically.