rust-security

Identify and mitigate security risks in Rust codebases including FFI boundaries and dependencies.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/juburr/mad-skills --skill rust-security-juburr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-security
Source: https://github.com/juburr/mad-skills/tree/main/rust-security
Command: npx skills add https://github.com/juburr/mad-skills --skill rust-security-juburr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides developers to write secure Rust code and to perform security reviews, helping identify unsafe usage, FFI boundaries, and dependency risks before shipping.

Core Features & Use Cases

  • Comprehensive guidance on safe vs unsafe Rust patterns, with concrete examples.
  • Checklists for FFI safety, panic safety, concurrency, and dependency management.
  • Real-world scenarios including code reviews, audits, and secure library design.

Quick Start

Ask the AI to perform a secure Rust review on your codebase focusing on unsafe usage, FFI boundaries, and dependency safety.

Frequently Asked Questions about rust-security

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

FAQPage Schema
How do I perform a security review on a Rust codebase with unsafe blocks and FFI boundaries?

To perform a Rust security review, analyze unsafe blocks and FFI boundaries for memory-safety issues and data leaks. Use guided checklists to identify concurrency pitfalls, panic safety risks, and crypto misuse across libraries and services.

What are common Rust security risks when using unsafe code and FFI?

Common Rust security risks include memory-safety violations within unsafe blocks and unchecked data passing across FFI boundaries. Additional risks involve deserialization flaws, concurrency pitfalls, and crypto misuse that can lead to data leaks.

How do I audit Rust dependencies for known security advisories?

Audit Rust dependencies for security advisories by checking them against rustsec advisories. Mitigate supply-chain risks by following dependency management checklists to identify vulnerable crates before shipping your project.

What is the best way to mitigate deserialization and concurrency vulnerabilities in Rust?

The best way to mitigate deserialization and concurrency vulnerabilities in Rust is to apply secure coding patterns and review checklists. This prevents panic safety issues and data races by guiding safe library design and data handling.

Does this Rust security guidance cover crypto misuse and supply-chain risks?

Yes, this Rust security guidance covers crypto misuse and supply-chain risks. It provides best-practice checklists and references to rustsec advisories to help prevent data leaks and dependency vulnerabilities during code reviews.