security-audit

To audit Rust dependencies for security vulnerabilities, this Skill uses Cargo for dependency resolution and cargo-audit for scanning. It identifies known vulnerabilities across both direct and transitive dependencies in your Rust project.

Beyond dependency vulnerabilities, a Rust security audit scans source code for unsafe patterns, hardcoded secrets, and input validation flaws. It also evaluates Cargo.toml and other configuration files for security best practices.

Yes, running a security audit requires both Cargo and cargo-audit. Cargo handles dependency resolution while cargo-audit performs the vulnerability scanning against the advisory database for your Rust project.

Run a security audit on your Rust codebase before deploying a new version to ensure all known vulnerabilities in dependencies, code, and configuration have been addressed. It is also useful when adding new dependencies to your project.

Finding unsafe code patterns in a Rust project is best handled by an automated audit that scans source files for unsafe blocks, hardcoded secrets, and input validation issues. This Skill combines code analysis with dependency vulnerability scanning and configuration review.