Vibe coding security scanner for AI-built apps
Built with Lovable, Bolt, Cursor, v0 or Replit? Check the app you deployed for public secrets and security configuration issues. Start with a limited scan, then use the evidence to decide what needs attention.
No signup for the instant security check. A free account adds the other audit tools.
Choose the scope you need
The instant scan, signed-in audit and active probes check different surfaces. Review which checks completed before interpreting a score.
No signup
Instant public scan
Start with headers, TLS, cookies and possible secrets in public page assets. Supabase queries and file-path probing are outside this limited check.
Free Basic account
Signed-in audit
Run the available public security checks, including Supabase discovery and count-only visibility checks, plus the other three tools. Basic includes 10 scans per month.
Eligible paid plan + ownership proof
Verified active checks
Choose limited active security probes on the exact hostname you verified. Review the evidence and coverage notes; a probe response is not proof that every route is safe.
Need source checks? Business adds GitHub source analysis, Gitleaks secret detection and OSV.dev npm dependency advisories. See plan coverage and limits.
What VibeShield can check
- Supported private-credential patterns in public HTML and JavaScript
- Security headers, HTTPS and cookie configuration
- Signed-in audits: supported exposed files and CORS checks
- Signed-in audits: anonymous Supabase table counts, without row contents
- Optional active checks after ownership verification and paid entitlement
- Separate accessibility, SEO & AEO, and Bundle & Tech tools with a free account
A missing header is a configuration observation. A public Supabase key can be intentional, and readable rows do not prove RLS is disabled. Review the Supabase RLS checker for what count-only evidence establishes.
Use it alongside your builder and database checks
Run your builder's checks before publishing, review the deployed URL, then test private workflows with disposable accounts. Lovable's security tools and Supabase's Advisors can review settings that a public scan cannot access.
Check both permitted and denied access for each sensitive workflow. A completed scan with no findings describes the scanned scope; it does not certify the whole app.
Start with the platform you use
From a finding to a reviewed change
- Read the finding and its response evidence. Check skipped or blocked areas.
- Explain the expected behavior to your coding assistant and ask for a focused fix.
- Review the patch, test permitted and denied actions, and deploy.
- Re-scan the same URL with comparable coverage. An incomplete or changed check cannot confirm resolution.
Secure Cursor deployment
Check the public build, production settings and server authorization before sharing a release.
Understand Supabase RLS results
Distinguish readable rows, zero-row responses and untested areas before changing a policy.
Turn scan results into a repair plan
Use the evidence to prioritize a change, preserve intended behavior and retest the deployed app.
Common questions
- What is a vibe coding security scanner?
- A vibe coding security scanner checks an app built with an AI coding tool for security observations within a defined scope. VibeShield starts with the deployed public URL. Signed-in Security audits can also inspect supported file paths, CORS configuration and anonymous Supabase table visibility.
- Can I scan without signup or source access?
- Yes. The anonymous instant scan checks security headers, TLS, cookies and possible secrets in public HTML or JavaScript. It needs no account, repository access or domain verification. Supabase API checks and file-path probes are part of signed-in audits, not the instant scan.
- When do I need to verify domain ownership?
- Signed-in public audits need no domain verification. Optional active security probes require ownership proof for the exact hostname, a paid entitlement and your authorization in the browser. They send limited probes for supported issues; they do not establish that every application workflow is secure.
- Does the scanner replace Lovable or Supabase's built-in checks?
- Use them together. Builder and database tools can inspect project settings or code that a public URL scan cannot see. VibeShield adds a deployed-site view. Test authenticated ownership and business workflows separately with disposable data.
- How do I fix a finding from an AI-built app?
- Review the response evidence, affected resource and coverage notes. Decide whether the observation conflicts with the app's intended behavior. Copy the fix prompt into your coding assistant, review its patch, test and deploy it, then re-scan the same URL.