Will It Vibe?Content-Security-Policy allows 'unsafe-inline' / 'unsafe-eval'
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
A CSP directive permits 'unsafe-inline' or 'unsafe-eval', which re-enables the inline-script and eval execution that CSP exists to block.
Why it matters
A Content-Security-Policy that includes 'unsafe-inline' or 'unsafe-eval' turns off the protections CSP is there to provide. With unsafe-inline, injected inline scripts and event handlers run; with unsafe-eval, string-to-code paths like eval keep working. An XSS bug that CSP would have blocked becomes exploitable again.
How to fix it
Remove 'unsafe-inline' and 'unsafe-eval' from script-src and style-src. Move inline scripts to external files, and where inline is unavoidable use per-response nonces or hashes instead of the blanket keyword. Refactor any eval/new Function usage so unsafe-eval is not needed. Roll the policy out in report-only mode first to find what breaks.
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