rmc-attribute-audit

To find deprecated Rust attributes in a workspace, you can search across the entire crate using prefix-anchored substring matching on attribute strings like #[deprecated. The audit correlates each finding with usage signals to help you assess whether deprecated items still have real consumers.

Yes, you can check must-use compliance by locating items with matching attributes and pairing that metadata with downstream caller analysis. By combining attribute matches with who_uses_summary, you can assess whether must-use contracts still have active consumers.

You can audit Rust doc comments by performing prefix-anchored substring matching across /// doc-comment bodies. This workspace-wide search tags match locations for clean triage, allowing you to extract precise context without reading the full source file.

Yes, inspecting Rust attributes requires a prebuilt HIR workspace hypergraph. You must build the hypergraph for your codebase first, and then you can run targeted attribute searches to plan safe refactors.

The best way to plan a deprecation migration is to identify items carrying specific attributes and connect those findings to downstream usage. This usage-aware combination allows you to prioritize follow-ups based on whether deprecated items still have real consumers.

Yes, you can identify items with non_exhaustive or cfg(test) attributes by running targeted workspace-wide attribute searches. These common audit recipes help you perform forward-compat checks and detect test-only code efficiently.