Windsurf · Supabase RLS check
Windsurf, from Codeium, uses agentic Cascade flows to edit code across a whole project. Deployment stays a manual step you own, same as Cursor.
Database rules are flagged as not-tested on every URL scan — a connected repo scan reviews your migrations and policy files directly instead.
What we look at for Windsurf
Wardloom always runs the full catalogue — these are the ones Windsurf projects most often get wrong, based on how the tool tends to generate and deploy code.
We review weak JWT secrets, missing rate limits, and insecure session patterns that show up in code and config.
Login is the front door. Soft session handling is how accounts get guessed, replayed, or shared without you noticing.
We look for server-only secrets used in the client, exposed dotfiles, and keys that belong behind the server wall.
AI scaffolds often put REACT_APP_ or NEXT_PUBLIC_ in front of secrets by habit. Config exposure is how private settings become public pages.
We scan your dependency tree for known-vulnerable or abandoned packages that still ship with the app.
Most vibe-coded stacks inherit risk from npm. Known CVEs are public; attackers do not need inventiveness, only an unpatched install.
Common Windsurf mistakes
What a scan like this can't see
Wardloom is honest about its limits. Database rules (Firestore RLS, Supabase RLS) is not something a read-only scan can verify from the outside — it requires a connected repo scan or a manual review. A clean result means nothing visible was wrong, not that everything was checked.
FAQ