Will It Vibe?Node TLS certificate verification disabled
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 15 points from that category, once per scan, no matter how many places it turns up.
What it detects
rejectUnauthorized: false turns off certificate validation for an HTTPS/TLS client, exposing traffic to man-in-the-middle attacks.
Why it matters
rejectUnauthorized: false tells the TLS client to accept any certificate, including self-signed or attacker-presented ones, which removes the protection HTTPS is supposed to provide. An attacker on the network path can then read and modify the traffic. This often starts as a workaround for a local certificate error and ships to production by accident.
How to fix it
Remove rejectUnauthorized: false and let validation run. If you are talking to a service with a private CA, add that CA to the ca option (or NODE_EXTRA_CA_CERTS) instead of disabling checks. For a genuinely local dev-only case, gate it behind an explicit non-production check and never let it reach a deployed 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