知识卡片
依赖审计需要覆盖传递关系
cargo-deny可按策略检查传递依赖中的已知安全、许可、禁止项及重复版本等问题。报告需结合配置、例外和实际可消除性判断,尤其不能一见多版就强制合并不同接口。定期运行能捕获上游新信息,但不能保证发现所有供应链风险。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter 4. Dependencies Solving Problems with Tooling · 查看原书依据
cargo-deny, which analyzes your dependency graph to detect a variety of potential problems across the full set of transitive dependencies: Dependencies that have known security problems in the included version Dependencies that are covered by an unacceptable license Dependencies that are just unacceptable Dependencies that are included in multiple different
参考来源
- 位置:《Effective Rust 35 Specific Ways to Improve Your Rust Code (David Drysdale)》第4章《Solving Problems with Tooling》(spine8;extracted/Effective Rust 35 Specific Ways to Improve Your Rust Code (David Drysdale)/_epub-src/OEBPS/ch04.html;u126-ch04-017)。
- 结论依据:原文在“cargo-deny”附近的定义、例子或代码支撑本卡核心说明:cargo-deny可按策略检查传递依赖中的已知安全、许可、禁止项及重复版本等问题。边界按已读前提解释;示例未执行。
- 原始内容:cargo-deny, which analyzes your dependency graph to detect a variety of potential problems across the full set of transitive dependencies: Dependencies that have known security problems in the included version Dependencies that are covered by an unacceptable license Dependencies that are just unacceptable Dependencies that are included in multiple different