3 advisory ignore entries no longer match anything in `Cargo.lock`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
Research direction
Open deny.toml and find the ignore list under [advisories]; the three ids to delete are RUSTSEC-2026-0097, RUSTSEC-2024-0436 and RUSTSEC-2026-0173. Confirm against Cargo.lock that rand is at or above the patched versions and that paste and proc-macro-error2 are absent, then run cargo deny check advisories to see the advisory-not-detected warnings disappear. Done means the 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 e1ef9e4ed83b, 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.lockis 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
- 12
- Forks
- 1
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/druid-operator
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/druid-operator#692 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
stackabletech/druid-operator#647 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
stackabletech/druid-operator#646 ·
Maintainers usually reply within 1 day
-
type/bug
Difficulty 5/5 Over a week Newbie friendliness 20/100
stackabletech/druid-operator#606 · 3 comments ·
Maintainers usually reply within 1 day
-
Server failing to create PoolableConnectionFactory. Failing with SCRAM-based authentication error.Opentype/bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
stackabletech/druid-operator#605 ·
Maintainers usually reply within 1 day
All issues in stackabletech/druid-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stackabletech/airflow-operator#898 ·
Maintainers usually reply within 1 day
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Possibly taken @zyl71 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bytecodealliance/wrpc#1785 ·
Maintainers usually reply within 1 day
-
2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day