3 advisory ignore entries no longer match anything in `Cargo.lock`
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
打开 deny.toml,找到 [advisories] 下的 ignore 列表;要删除的三个 id 是 RUSTSEC-2026-0097、RUSTSEC-2024-0436 和 RUSTSEC-2026-0173。对照 Cargo.lock 确认 rand 处于已修补版本或更高版本,并且 paste 和 proc-macro-error2 不存在,然后运行 cargo deny check advisories,看到 advisory-not-detected 警告消失。完成意味着这些条目已删除,检查干净通过。
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Rust
- 星标
- 12
- 派生
- 1
- 平均合并
- 16 小时 22 分钟
- 30 天内合并 PR
- 13
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
stackabletech/druid-operator 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 35/100
stackabletech/druid-operator#692 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 45/100
stackabletech/druid-operator#647 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 30/100
stackabletech/druid-operator#646 ·
维护者通常 1 天内回复
-
type/bug
难度 5/5 一周以上 新手友好度 20/100
stackabletech/druid-operator#606 · 3 条评论 ·
维护者通常 1 天内回复
-
Server failing to create PoolableConnectionFactory. Failing with SCRAM-based authentication error.未关闭type/bug
难度 4/5 3-5 天 新手友好度 25/100
stackabletech/druid-operator#605 ·
维护者通常 1 天内回复
查看 stackabletech/druid-operator 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 1/5 1 小时以内 新手友好度 82/100
stackabletech/airflow-operator#898 ·
维护者通常 1 天内回复
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)可能已有人在做 @zyl71 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
-
难度 1/5 1 小时以内 新手友好度 88/100
bytecodealliance/wrpc#1785 ·
维护者通常 1 天内回复
-
2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)未关闭
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复