Will It Vibe?Session cookie Secure flag 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
A cookie or session store sets secure: false, so the cookie is transmitted over cleartext HTTP and can be intercepted on the network.
Why it matters
secure: false lets the browser send the cookie over plain HTTP, where anyone on the network path can read it. For a session or auth cookie that means the session can be captured on any unencrypted hop. The flag is often added to make local development work and then ships to production unchanged.
How to fix it
Set secure: true for session and auth cookies in production, and drive the value from an environment flag so local HTTP still works (secure: process.env.NODE_ENV === "production"). Pair it with httpOnly: true and an appropriate sameSite value. Make sure your app runs behind HTTPS in every deployed environment.
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