unsafe-checker

Auditing unsafe Rust code involves identifying patterns that threaten memory safety and FFI boundaries. This process surfaces violations, ensures safety invariants are documented with SAFETY comments, and generates structured reports to guide code reviews.

Documenting safety invariants for cross-crate unsafe Rust interfaces involves applying standardized templates like SAFETY comments and Safety sections. This ensures unsafe boundaries are explicitly reasoned about and mitigated against bad patterns.

Generating safe wrappers for performance-critical Rust primitives is supported by providing actionable safety guidance. It analyzes unsafe usage and suggests safe abstractions to ensure soundness while maintaining performance where unsafe code is necessary.

Static analysis works for checking FFI safety and panic-safety in Rust by applying centralized lint rules. It identifies unsafe boundaries and bad patterns, ensuring comprehensive risk assessment and invariant documentation across the codebase.

You need to run an unsafe Rust code review checklist when working with codebases that have extensive unsafe usage, cross-crate unsafe interfaces, or performance-critical primitives. It surfaces violations and produces workflow-ready outputs for auditors.