VibeShieldVibeShield
Security scanner for Bolt apps

Free Bolt security scanner

Bolt builds apps from a prompt. Identify your app's actual framework, backend and host first. If it uses Vite, client-exposed VITE_ values must contain public configuration rather than private credentials.

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.

See a Bolt scan walkthrough

A 30-second walkthrough of scan options and an example finding.

What we check on Bolt apps

Typical stack: Confirm your framework, Bolt Cloud or other backend, and deployment host

The no-signup scan checks headers, TLS, cookies and public HTML/JavaScript exposure. The checks below describe broader account audits; database access and authenticated workflows also need manual testing. Results include evidence, individual check outcomes and coverage limitations.

Secrets in VITE_ variables

Vite can expose VITE_ values to browser code. VibeShield checks inspected public HTML and JavaScript for supported private-credential patterns.

Supabase tables anyone can read

If your app uses Supabase, its browser-suitable public key is visible by design. VibeShield checks anonymous visibility of discovered tables using row counts, without fetching row data. Review whether visible rows are intentionally public; this alone does not prove RLS is disabled.

Exposed source maps

A public source map can expose readable source code. Signed-in security audits check for valid, reachable maps referenced by inspected same-origin JavaScript.

Missing security headers

Review CSP, HSTS and framing protection on the deployed response. Missing headers are configuration risks, not proof of a working exploit. Test the suggested policy with login and integrations before enforcing it.

Educational scenario · manual testing in your own staging app

Trace an email integration from the browser to the server

  1. List environment-variable names and classify their purpose without recording secret values.
  2. For a Vite frontend, inspect VITE_ references. Move private email or payment API calls behind a server function; renaming a variable alone is insufficient.
  3. Use a harmless marker in staging to check build exposure. Test the server's request validation and abuse controls, then rebuild and inspect the published bundle.

Ask Bolt for a focused review

Trace my email integration. Keep public configuration in the frontend and private credentials on the server. Validate requests and restrict recipients. Show a focused diff and tests for allowed and denied requests without printing secret values.

These tests extend beyond a public URL scan. Read the Bolt testing guide and consult Vite environment-variable guidance.

For public exposure checks, scan your app for free. Account audits need no domain verification; active probes require a verified hostname and an eligible plan.

Found something? Fix it in Bolt.

  • Start with your live URL — no signup for the limited first security scan
  • Signed-in audits cover passive security, accessibility, SEO & AEO, and bundle without domain verification
  • Every issue explained in plain English, ranked by what to fix first
  • Account reports include AI-ready prompts to help your coding tool propose fixes you can review and test

Want to keep checking after changes? Pro adds weekly schedules, email alerts, and active attack checks (after verification). Business adds deploy webhooks, daily schedules, Slack/Discord/ClickUp alerts, and GitHub source scanning with Gitleaks and OSV.dev.

Also built with: Lovable · v0 · Cursor · Replit