How 10 open source projects manage unsafe code
summary
Survey of ten open source projects finds concrete policies: projects like Servo and cargo-geiger use deny/forbid at crate root to block accidental unsafe, others pack all unsafety into one module or crate so a memory allocator or storage engine isolates risks, cryptography crates use intrinsics inside minimal unsafe wrappers, and teams require a comment explaining each unsafe block plus CI lints and tools like cargo-geiger and clippy. Examples include a Windows runtime wrapper, a Firecracker-style VM component, and a fast rsync binding that all work under these constraints.
AI-written summary · about
chapters (4)
related talks
45mBuilding Safe and Secure Systems in Rust
19mCounterexamples in Safe Rust
23mSecure Code, Safe Future: Mastering Security in Critical Software Development
15mHow Do Programmers Use Unsafe Rust?
30mSecure Open Source Practices
01h 01mSoftware Security
46mPanel: Rust in Safety Critical
50mCrate security in 2025