unsafe-checker

To enforce SAFETY comments for unsafe Rust blocks during code review, the checker identifies every unsafe block and verifies that explicit SAFETY: notes documenting invariants are present, flagging violations and suggesting fixes.

The best way to verify invariants across unsafe Rust APIs and FFI boundaries is to analyze raw pointers, unions, and memory layout concerns, ensuring documented safety contracts are validated and safe interop is maintained.

Yes, you can use static analysis to check memory safety in Rust codebases at scale by running safety review passes that verify data-flow validations and safety invariants across teams during audits and inline checks.

Yes, the review process provides actionable fixes for FFI and memory-safety violations by analyzing raw pointers and unions, offering reviewer guidance and recommended fixes to correct documented invariant discrepancies.

You need to document safety contracts for unions and raw pointers in Rust whenever unsafe blocks or FFI boundaries are present, ensuring memory layout concerns and safety invariants are explicitly verified to avoid common pitfalls.