Will It Vibe?Wildcard CORS allowed origins in config
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
An allowed-origins config value is "*", so any website can make browser requests to the API. Combined with credentialed requests this exposes authenticated endpoints to cross-site abuse.
Why it matters
An allowed-origins value of "*" lets any website make browser requests to your API. If the API also allows credentials, a malicious page can read authenticated responses on behalf of a logged-in user. The wildcard is often copied in during debugging and then forgotten.
How to fix it
Set the allowed origins to the specific front-end origins that need access, read from an environment variable per environment. Never combine a wildcard origin with credentialed requests. Confirm requests from an unlisted origin are refused by the browser.
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