Clickjacking protection disabled
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
Framing protection is turned off: X-Frame-Options set to ALLOWALL, helmet frameguard: false, or a CSP frame-ancestors that allows any origin.
Why it matters
Framing protection stops other sites from loading your pages inside an invisible iframe and tricking users into clicking hidden controls (clickjacking). Setting X-Frame-Options to ALLOWALL, disabling helmet frameguard, or using a wildcard frame-ancestors removes that protection, so any site can frame you.
How to fix it
Deny framing by default. Set X-Frame-Options to DENY, or SAMEORIGIN if your own pages frame each other, and back it with a CSP frame-ancestors directive listing only the origins allowed to embed you (use frame-ancestors none when none should). In helmet, keep frameguard enabled rather than disabling it.
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