VibeShieldVibeShield

Security checklist

The vibe-coding security checklist

11 things to check before you launch an app built with Lovable, Bolt, v0, Cursor or Replit. A free account can automate several checks; review the remaining items manually. Plan labels show related scanner coverage, not proof that every step in an item was tested. The no-signup scan has a smaller security-only scope.

  1. 1Review RLS and grants for each exposed Supabase table

    Relevant checks: Basic account

    Why: Your browser-suitable key is public by design. Grants and RLS policies determine what visitors can access; anonymous readability alone does not prove RLS is disabled.

    Enable RLS on exposed tables, restrict grants to required operations and test policies against intended public, owner and team access with synthetic users.

  2. 2Keep secret keys out of the browser

    Relevant checks: Basic account

    Why: An OpenAI, Stripe secret or Supabase service_role key in your JavaScript can be copied by anyone and run up your bill or open your data.

    Call those APIs from a server route or edge function, and use only publishable keys in the frontend.

  3. 3Never put secrets in VITE_ or NEXT_PUBLIC_ variables

    Relevant checks: Basic account

    Why: Build tools copy these straight into the code your visitors download.

    Move private API calls and credentials to server code, restrict what that endpoint permits, rebuild and inspect the published bundle. Renaming a variable alone is insufficient.

  4. 4Require email confirmation on sign-up

    Relevant checks: Basic account

    Why: Otherwise anyone can create accounts with email addresses they don't own.

    In Supabase: Authentication → Providers → Email → turn on “Confirm email”.

  5. 5Set the security headers

    Relevant checks: Basic account

    Why: CSP, HSTS, framing protection and content-type protection can reduce specific browser risks. Missing headers do not prove an exploitable vulnerability.

    Add them in your host's config (vercel.json, netlify.toml) or your framework's headers setting.

  6. 6Make sure .env, .git and backups aren't public

    Relevant checks: Basic account

    Why: A misconfigured host can hand out your environment file or entire git history.

    Keep them out of your public/ folder and deploy output; block dotfiles at the server.

  7. 7Lock down CORS

    Relevant checks: Basic account

    Why: Reflecting an untrusted origin while allowing credentials can expose authenticated responses, depending on the endpoint and cookie behavior. Wildcard origins do not permit credentialed browser reads.

    Allow the origins your app needs and test sensitive API responses. Review deliberate public APIs separately.

  8. 8Rate-limit login, sign-up, password reset and AI endpoints

    Do it yourself

    Why: Unlimited attempts invite credential stuffing — and an open AI route can burn through your API budget overnight.

    Add rate limiting at the edge or in middleware and test the actual submission endpoints in staging. A bounded URL scan cannot prove login or AI-request throttling.

  9. 9Check permissions on the server, not only in the UI

    Do it yourself

    Why: Hiding an admin button isn't protection — the page or API behind it must refuse requests too.

    Verify the user's session and role in every server route and database policy.

  10. 10Rotate any key that was ever exposed

    Do it yourself

    Why: Deleting a leaked key from your code doesn't un-leak it — it's in your git history and possibly in someone's hands.

    Generate a new key in the provider's dashboard and revoke the old one.

  11. 11Re-check after every deploy

    Relevant checks: Business

    Why: Every new prompt can change your app — and quietly undo a fix.

    Use a deploy webhook (Vercel, Netlify, or any CI) so each successful deploy triggers a scan and alerts on new critical/high issues.

Start with the public checks, then test your access rules

Free instant security scan, no signup. Audits need no verification. Active security probes require ownership proof (meta or .well-known).

No signup or domain verification. See findings, evidence, check-by-check coverage and a score when checks complete. Checks cover headers, TLS, cookies and public HTML/JS exposure. A free account adds all four tools and AI fix prompts.