unsafe-checker

To check unsafe Rust code for missing SAFETY comments, scan .rs source files to detect unsafe blocks, raw pointers, FFI, and transmute patterns, then validate the presence of required SAFETY comment annotations.

Unsafe Rust constructs requiring SAFETY documentation include raw pointers, FFI bindings, transmute operations, and unsafe blocks, ensuring alignment, initialization, and thread-safety requirements are explicitly validated.

Review Rust FFI and transmute patterns by scanning source files for risky constructs and validating that required SAFETY comments address alignment, initialization, and thread-safety requirements to prevent undefined behavior.

Yes, this unsafe code checker can scan any Rust project by analyzing .rs files across the entire codebase to detect unsafe keywords, raw pointers, and related risky patterns.

The best way to find safer alternatives for unsafe Rust blocks is to scan source files for risky patterns, validate missing SAFETY comments, and reference quick reference tables for recommended crates.

Rust code fails safety checks for raw pointers when missing SAFETY comments fail to validate alignment, initialization, and thread-safety requirements for unsafe blocks and transmute operations.