Unlocking the full potential of Cargo extensions in Rust development
summary
Cargo is a package manager not a full build system, so large repos hit caching and CI pain and some people use Bazel for faster large builds; specific extensions that matter are described and how to use them: cargo-deny in CI enforces license and advisory checks and suggests fixes, cargo-udeps on large repos finds unused dependencies (used to clean crater/Pathfinder clones), cargo expand for macro debugging shows exact expanded code, cargo-watch runs lightweight background checks, and beware security vectors like replacing rustc or aliasing cargo subcommands (cargo-audit can be aliased to run arbitrary code).
AI-written summary · about
chapters (8)
- 0:00Cargo in Rust
- 3:25Cargo extensions value
- 7:26Security risks with Cargo
- 11:04Built-in Cargo extensions
- 15:12Advanced Cargo extensions
- 20:06Cargo Deny
- 22:36Workspace dependency management
- 24:26Summary
related talks
16mCargo, or how to extend Rust tooling to infinity!
32mBuilding and Maintaining Rust at Scale
37mWrapping Cargo for Shipping
27mParsing Rust code considered harmful
21m"What Happens When You Run Cargo Build?"
50mCrate security in 2025
45mBuilding Safe and Secure Systems in Rust
26m"Finding Bugs with cargo-mutants"