unsafe-checker

Reviewing unsafe Rust code involves analyzing unsafe blocks for raw pointer risks, undefined behavior, and FFI soundness issues. It verifies invariants, checks panic safety, and ensures proper memory layout to prevent critical vulnerabilities.

Ensuring FFI safety requires analyzing interactions with C libraries for soundness issues and undefined behavior. You must verify raw pointer usage, document invariants with `SAFETY` comments, and check panic safety to maintain safe boundaries between Rust and C code.

Writing `SAFETY` comments involves documenting the specific invariants and preconditions that uphold memory safety in unsafe Rust. You must detail why raw pointer operations, FFI interactions, and memory layouts are sound and free from undefined behavior.

Yes, checking for panic safety in low-level Rust data structures is a core function. It analyzes critical unsafe code sections to identify panic safety issues, ensuring unexpected panics do not violate memory safety invariants or cause undefined behavior.

Common pitfalls when using raw pointers in unsafe Rust include pointer aliasing, invalid memory layouts, and triggering undefined behavior. Analyzing unsafe code helps identify these risks, ensuring soundness and verifying that all safety invariants are properly documented.

You need to analyze unsafe Rust code for soundness issues when implementing low-level data structures or interacting with C libraries via FFI. This analysis identifies undefined behavior risks, verifies `SAFETY` comments, and ensures raw pointer operations maintain memory safety.