Will It Vibe?Authentication disabled in service 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
Config turns authentication off (security.enabled=false, disable_auth=true, auth: none). A service that ships with auth disabled is reachable by anyone who can route to it, including via a misconfigured environment.
Why it matters
Config that turns authentication off makes the service reachable by anyone who can route to it. This is often set for a local demo and then carried into an environment where the service is exposed. An unauthenticated admin or data endpoint is one of the most direct routes to a breach.
How to fix it
Re-enable authentication in the config and drive any relaxed setting from an environment variable that stays off outside local development. Confirm the service rejects unauthenticated requests. If a component genuinely must run without auth, isolate it to a private network rather than exposing it.
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