Will It Vibe?Crate/module-wide #![allow(clippy::all)]
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 2 points from that category, once per scan, no matter how many places it turns up.
What it detects
A crate- or module-wide #![allow(clippy::all)] disables every Clippy lint for everything beneath it, hiding real findings along with whatever noise motivated the suppression.
Why it matters
A crate- or module-wide #![allow(clippy::all)] turns off every Clippy lint for everything beneath it, including lint categories that catch real bugs (like clippy::correctness), not just style nitpicks. Whatever noisy lint motivated the blanket suppression gets fixed by hiding it, along with every future finding Clippy would have surfaced in that scope.
How to fix it
Remove the blanket suppression and run cargo clippy to see what it actually flags. Fix genuine issues, and for any lint that is a deliberate, informed disagreement with the project's style, suppress only that specific lint at the narrowest scope that needs it (a single #[allow(clippy::specific_lint)] on the item, with a short comment explaining the choice) rather than disabling the whole lint group.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo