awesome-rust-security-guide
github.com/ianonymous3000/awesome-rust-security-guide ↗Where Rust's safety guarantees stop, and how to secure Rust code, dependencies, builds and services. Every claim sourced, every example compiled in CI.
21
GitHub Stars
58
Curated Resources
14
Categories
12 hours ago
Last Refreshed
What Rust does and doesn't protectIs this crate safe to depend on?Supply chain, releases, responseUnsafe and FFIConcurrency and asyncAuditing Rust codeCrypto, TLS, secretsHardening a serviceWhich tool finds which bugBinary hardening and sandboxingDomains: embedded, kernel, Wasm, safety-criticalPrivacy techCasebookStay current
Use this list with your AI agent
Add the Context Awesome MCP server to Claude, Cursor, or any MCP client, then ask:
"Show me is this crate safe to depend on? resources from awesome-rust-security-guide"
Installation instructions →What's inside
Is this crate safe to depend on?
Casebook
- 2018–2021
std buffer overflows, double frees
- 2022-01-20
std symlink race
- 2024-02-16
cve-rs: memory corruption without
- 2024-04-09
Windows batch-file injection in
- 2024-06-18
curve25519-dalek leaked timing
- 2025-09-12
phishing for GitHub logins
Auditing Rust code
- ANSSI guidelines
- AUD-6
CORS: any origin, with credentials
- Check Point's Akira teardown
- CodeQL Rust queries
What Rust does and doesn't protect
Supply chain, releases, response
Concurrency and async
- CON-4client disconnects
, then (tokio ≥1.53.2 ; 1.51.x: ≥1.51.5 )
- loom 0.7.2
- Oxide RFD 400
Which tool finds which bug
Domains: embedded, kernel, Wasm, safety-critical
Showing a sample of 58 resources. View the full list on GitHub →