Will It Vibe?@CrossOrigin wildcard origin with credentials allowed
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
@CrossOrigin allows any origin ("*") while also setting allowCredentials=true, so cookies and Authorization headers would be sent on cross-origin requests from literally any site. Modern browsers reject a literal wildcard combined with credentials, but this configuration still indicates the intent and often ships alongside a permissive allowed-origin-patterns fallback that does work.
Why it matters
Combining a wildcard origin with allowCredentials=true asks the browser to send cookies and Authorization headers on cross-origin requests from literally any site. Modern browsers refuse a literal "*" alongside credentials, but this configuration shows the intent, and it is frequently paired with a permissive allowed-origin-patterns fallback elsewhere that actually does work, silently reintroducing the same exposure.
How to fix it
Replace the wildcard with an explicit, small allow-list of trusted origins, keep allowCredentials=true only if the endpoint genuinely needs cookies/auth headers cross-origin, and verify the effective configuration (including any global CorsConfigurationSource) does not fall back to a pattern that re-admits every origin.
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