Will It Vibe?Go InsecureSkipVerify enabled
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
tls.Config{InsecureSkipVerify: true} disables certificate and hostname verification for the connection.
Why it matters
tls.Config{InsecureSkipVerify: true} disables both certificate and hostname verification for the connection, so any certificate is accepted and the TLS guarantee is gone. An on-path attacker can impersonate the server. This is frequently copied from a snippet that was only meant for local testing.
How to fix it
Set InsecureSkipVerify to false (or omit it). For a private CA, build a tls.Config with a RootCAs pool loaded from your CA certificate. If you need to verify against a specific name, set ServerName rather than skipping verification. Keep the insecure flag out of anything that runs in production.
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