rust-quality

Automate Rust code quality audits by scanning crates and workspaces to generate structured reports. The audit checks Clippy violations, borrowing, option handling, and error management, outputting categorized sections for critical issues, warnings, and suggestions.

A Rust static analysis report includes categorized sections for critical issues, warnings, and suggestions. It specifically evaluates Clippy violations, borrowing and cloning patterns, iterator usage, error handling, performance, documentation, and type system adherence.

Yes, you can vet Rust pull requests by running the audit to flag common borrowing and cloning patterns that lead to inefficiencies or ownership issues. It produces a structured report highlighting these concerns alongside other critical warnings.

Enforce Clippy checks in a Rust workspace by applying the audit to ensure all warnings are addressed, avoid bare allows, and verify that workspace lint config is present. The audit systematically reviews the codebase for these specific violations.

The best way to check Rust iterator patterns and option handling is to run a comprehensive code quality audit. It evaluates these implementation patterns alongside error handling and type system usage, returning a structured report of suggestions and warnings.

Yes, the Rust audit explicitly checks both documentation and type system usage. It incorporates these checks into a comprehensive review that also covers performance and error handling, generating a structured report with critical findings and suggestions.