skills.rest
kocakburhan
kocakburhanCOMMUNITY
Explore all skills by this author →
GitHub

sc-lang-rust

Identify Rust security anti-patterns and unsafe code risks with CWE mappings.

Updated Aug 23, 2026
Search Tags:#security#concurrency#rust#static-analysis#ffi#unsafe-blocks
One-click install
npx skills add https://github.com/kocakburhan/emlakdefter --skill sc-lang-rust-kocakburhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sc-lang-rust
Source: https://github.com/kocakburhan/emlakdefter/tree/main/.agents/skills/security-check/skills/sc-lang-rust
Command: npx skills add https://github.com/kocakburhan/emlakdefter --skill sc-lang-rust-kocakburhan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rust developers face subtle security risks in unsafe code, FFI boundaries, and concurrency patterns that can undermine safety guarantees. This skill identifies rust-specific anti-patterns and provides concrete remediation guidance.

Core Features & Use Cases

  • Automated Rust security checks: detects unsafe blocks, risky FFI usage, and concurrency pitfalls across codebases.
  • Conformance with Rust security best practices: aligns findings with the Rust security checklist to guide fixes.
  • Use Case: in a Rust project, scan a crate to surface unsafe blocks, potential undefined behavior, and crate misuse, then produce actionable remediation notes.

Quick Start

Run the sc-lang-rust security scan on your Rust project to surface unsafe patterns and checklist-aligned remediation.

Frequently Asked Questions about sc-lang-rust

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

FAQPage Schema
How do I scan a Rust project for unsafe blocks and FFI security risks?▼

Scanning a Rust project for unsafe blocks and FFI security risks involves detecting anti-patterns across codebases and CI pipelines, then producing actionable findings with CWE mappings and checklist-aligned remediation guidance.

What are common Rust concurrency pitfalls and how are they detected?▼

Rust concurrency pitfalls are detected by scanning code repositories for risky patterns that undermine safety guarantees, then generating concrete remediation notes aligned with the Rust security checklist.

Can I integrate Rust static analysis into CI pipelines for continuous security checks?▼

Rust static analysis can be applied across CI pipelines to continuously identify unsafe code risks, FFI boundary issues, and crate misuse, producing actionable findings with CWE mappings for remediation.

What is the best way to map Rust security findings to known vulnerability classifications?▼

Mapping Rust security findings to known classifications is best handled by generating findings with CWE mappings and references to the rust-security-checklist, providing verifiable and standardized remediation guidance.

Does static analysis detect crate misuse and undefined behavior in unsafe Rust code?▼

Static analysis detects crate misuse and potential undefined behavior in unsafe Rust code by identifying specific anti-patterns at FFI boundaries and within unsafe blocks, yielding actionable remediation notes.

Related Skills

Explore More Software Engineering Skills→
peancharoenpeancharoen

speckit.checker

Run static analysis tools to detect linting, type, and security issues across source code.

Community
Advanced
woohyun212woohyun212
21

secure-code-review

Identify CWE-mapped security weaknesses across 10 code review domains.

Community
Intermediate
truongnattruongnat

security-review

Audits code for OWASP Top 10 vulnerabilities, hardcoded secrets, and unsafe patterns.

Community
Advanced
PriyanshKuniyalPriyanshKuniyal

sast-configuration

Configures and manages SAST tools for automated vulnerability detection in CI/CD pipelines.

Community
Advanced