rust-security

Audit Rust dependencies for vulnerabilities and enforce cargo-deny policies.

58|4|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/po4yka/RIPDPI --skill rust-security-po4yka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-security
Source: https://github.com/po4yka/RIPDPI/tree/main/.claude/skills/rust-security
Command: npx skills add https://github.com/po4yka/RIPDPI --skill rust-security-po4yka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rust projects face supply-chain vulnerabilities and outdated crates; this skill helps teams audit, govern, and triage dependencies to prevent CVEs from impacting builds and runtime behavior.

Core Features & Use Cases

  • Audit dependencies with cargo-audit: detect known advisories in Rust crates used by your project.
  • Enforce policies with cargo-deny: apply license, bans, and source checks in CI and local development.
  • RUSTSEC triage and risk mitigation: prioritize advisories, track ignores, and plan upgrades or pinning.
  • Pre-purchase crate risk assessment: evaluate new crates for typosquats before adding them to Cargo.toml.
  • Use Case: when onboarding a new dependency, run audits and policy checks to avoid risky crates.

Quick Start

Install cargo-audit and cargo-deny, run the checks against native/rust/Cargo.toml, and triage advisories before adding a new crate.

Frequently Asked Questions about rust-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Rust dependencies for known vulnerabilities?

To audit Rust dependencies for vulnerabilities, run cargo-audit against your project's Cargo.toml to detect known RUSTSEC advisories. This skill helps triage identified risks and plan necessary crate upgrades or pinning.

What is the best way to enforce license and source policies in a Rust CI workflow?

Enforcing license and source policies in a Rust CI workflow is best done using cargo-deny with a configured deny.toml file. This skill applies ban checks and policy enforcement across local and CI environments.

How do I check a new Rust crate for typosquatting before adding it to Cargo.toml?

To check a new Rust crate for typosquatting before adding it to Cargo.toml, perform a pre-purchase risk assessment using this skill. It evaluates new dependencies to prevent risky supply-chain additions.

Do I need cargo-audit and cargo-deny installed to triage RUSTSEC advisories?

Yes, you need cargo-audit and cargo-deny tooling installed to triage RUSTSEC advisories effectively. This skill requires these tools and up-to-date Rust crates metadata to perform checks and track ignores.

When do I need to run supply-chain checks for Rust crates?

You need to run supply-chain checks for Rust crates when onboarding a new dependency or updating builds to prevent CVEs. This helps mitigate runtime risks by auditing dependencies before they impact behavior.