Will It Vibe?Cleartext HTTP endpoint in fetch
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A fetch() call targets a hardcoded http:// URL (not localhost), sending the request and any credentials over an unencrypted connection that can be read or tampered with in transit. Use https.
Why it matters
A fetch() to a hardcoded http:// URL sends the request over an unencrypted connection, so anyone on the network path can read the response and any headers or tokens sent with it, and can tamper with the reply. For server-to-third-party calls this exposes data in transit that users assume is protected.
How to fix it
Change the URL to https:// if the endpoint supports it (most do). If the value varies by environment, read it from an environment variable that holds an https URL. Only plain localhost during development should remain on http.
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