3 advisory ignore entries no longer match anything in `Cargo.lock`

Open Beginner friendly
#898 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
82/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
security

Research direction

Open deny.toml and find the [advisories] section's ignore list; the three ids RUSTSEC-2026-0097, RUSTSEC-2024-0436 and RUSTSEC-2026-0173 are on active lines there and are the only lines to delete. Confirm against Cargo.lock that rand is at 0.9.5/0.10.3 and that paste and proc-macro-error2 are absent, then run cargo deny check advisories to confirm no advisory-not-detected warnings remain. Done means the three entries are gone and the check passes cleanly.

Written by the indexing model from the issue text.

Description

Hi, and thanks for maintaining this project.

deny.toml still ignores the advisories below. Cargo.lock on the default branch either already holds a patched version of the affected crate or no longer contains the crate, so the entries no longer suppress anything and can be removed.

Advisory Summary In Cargo.lock now Patched in Severity
RUSTSEC-2026-0097 Rand is unsound with a custom logger using rand::rng() rand 0.10.3, 0.9.5 0.8.6, 0.9.3, 0.10.1 low
RUSTSEC-2024-0436 paste - no longer maintained paste: not present – unmaintained
RUSTSEC-2026-0173 proc-macro-error2 is unmaintained proc-macro-error2: not present – unmaintained

What we checked on 2026-11-21, on the default branch at commit b1168be2ed15, by reading public files only:

  • Each id is on an active (non-comment) line of the file.
  • For each advisory, no version of the affected crate in Cargo.lock is inside its affected range.

Why it is worth removing: 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 or came back into the lock file, cargo-deny would stay silent about it.

For cargo-deny, such entries show up as advisory-not-detected warnings. Setting unused-ignored-advisory = "deny" under [advisories] turns them into errors, so an entry cannot outlive the lock file it was written for.

Disclosure: the check and this text were produced with automated tooling, including an LLM. The repository files were re-read from the default branch on 2026-11-21.

Feel free to close this if it is not useful.

Dominant language
Rust
Stars
32
Forks
6
Avg merge
1d 6h
Merged PRs (30d)
12

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/airflow-operator

All issues in stackabletech/airflow-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.