Repository navigation
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.
Closes #61
deny.tomlstill ignores the advisory below, butCargo.lockonmainalready holds a patched version of the crate, so the entry no longer suppresses anything. This pull request removes it, together with the comments that explained it.Cargo.locknowruzstd: a tiny input can exhaust memory (OOM)ruzstd0.9.1Why remove it. An ignore entry keeps muting the advisory id for as long as it stays in the file. If the crate were later pinned back to an affected version, cargo-deny would stay silent about it.
What was checked, and what was not.
mainat commit334ad3fec0caon 2026-11-20: the id is on an active line of the config, and no version of the affected crate inCargo.lockis inside the affected range of its advisory (RustSec records).deny.toml. No Rust source and no lock file is changed. The edited file parses as TOML, and every other ignore entry and setting is unchanged.cargo deny check advisorieslocally, because we do not build or execute anything from this repository. CI is the first run of the tool on this change.Not part of this change, but possibly useful: cargo-deny reports such entries as
advisory-not-detectedwarnings, andunused-ignored-advisory = "deny"under[advisories]turns them into errors.Disclosure: the check, the edit and this text were produced with automated tooling, including an LLM.
Feel free to close this if it is not useful.