Will It Vibe?ESLint disabled during builds
Part of Testing & CI, which counts for 10% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
eslint.ignoreDuringBuilds: true skips linting during next build, so lint failures (including security lint rules) no longer block a release. The safety net only runs where someone remembers to run it by hand.
Why it matters
eslint.ignoreDuringBuilds: true skips linting during next build. Lint rules, including security-oriented ones and the Next.js rules that catch real mistakes, no longer block a release, so problems ship whenever no one runs the linter by hand. The build stops being a reliable gate.
How to fix it
Remove ignoreDuringBuilds so linting runs in the build again, and fix or explicitly disable individual rules that are noisy. If lint is slow in CI, run it as a separate required job rather than turning it off in the build.
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