rmc-unsafe-audit

Rust unsafe audit tools check for a `SAFETY` comment within the five source lines preceding the `unsafe` keyword. If the heuristic finds no `SAFETY` text in that window, the block is flagged as undocumented for review.

The best way to prioritize unsafe code review is calculating a blast radius using `recursive_callers_count`. This ranks undocumented `unsafe { ... }` blocks by how many transitive callers touch the enclosing function, weighing risk by exposure.

A call graph helps audit Rust unsafe blocks by building a workspace hypergraph to compute transitive caller counts. This identifies the enclosing function identity for each `unsafe { ... }` span and ranks review priority by blast radius.

Yes, you can audit safety comments across an entire Rust workspace by enumerating every `unsafe { ... }` span. The audit extracts file spans, line counts, and enclosing function identities to return structured findings for review.

Reviewing undocumented Rust unsafe blocks requires surrounding source context extracted using `read_file_content`. This pulls the code around the `unsafe` keyword to validate whether an existing `SAFETY` comment matches the actual invariant.