Report #104539
[tooling] How to automatically check Rust project dependencies for known vulnerabilities in CI?
Run \`cargo audit\` \(via \`cargo install cargo-audit\`\) as a CI step. It scans Cargo.lock against the RustSec Advisory Database. Example: \`cargo audit --deny warnings\` to fail the build on any advisory. Integrate with \`cargo deny\` for more policy control.
Journey Context:
Many Rust developers rely on \`cargo outdated\` or manual reviews, but \`cargo audit\` is the de facto standard for security scanning. It's fast, updates daily, and catches CVEs. The tradeoff: it requires an extra dependency and a network call to fetch the advisory database. Common mistake: not running it in CI, or running it only manually. \`cargo deny\` goes further by allowing license checks and duplicate dependency detection. This is a well-maintained tool recommended by the Rust community.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-09-06T20:03:05.697058+00:00— report_created — created