Will It Vibe?Python 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
verify=False (requests/httpx), ssl.CERT_NONE, or an unverified SSL context skips certificate checks and enables man-in-the-middle attacks.
Why it matters
verify=False (requests/httpx), ssl.CERT_NONE, or an unverified SSL context makes the client accept any certificate, so a man-in-the-middle can present their own and read or alter the traffic. requests also emits an InsecureRequestWarning for exactly this. It commonly lingers after someone silenced a local certificate error.
How to fix it
Remove verify=False and let verification run. For an internal CA, pass verify="/path/to/ca-bundle.pem" (or set REQUESTS_CA_BUNDLE) instead of turning checks off. For client certs use the cert parameter. If a script genuinely must skip verification for a local sandbox, isolate it and keep it out of production paths.
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