Will It Vibe?CSRF_COOKIE_SECURE 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
CSRF_COOKIE_SECURE = False allows the CSRF cookie to be sent over plain HTTP, so it can be captured on the wire by anyone positioned between the client and the server.
Why it matters
CSRF_COOKIE_SECURE = False allows the CSRF cookie to be sent over plain HTTP. Captured on the wire, that token by itself is not enough to forge a request (the attacker still needs to get it into a form submission), but it removes one layer of the defense and is inconsistent with treating the same connection as secure everywhere else.
How to fix it
Set CSRF_COOKIE_SECURE = True in any settings served over HTTPS, matching SESSION_COOKIE_SECURE. Drive both from the same environment-based flag so they can never drift out of sync between environments.
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