By the PrototypeVerdict Test Team · Pattern sources read Nov 9, 2026 · Pairs with our vibe-coding security checklist
Our Bolt and Lovable links are referral links: if you sign up through one, Bolt or Lovable may reward us, at no extra cost to you. How we make money.
← All free AI app builder tools
This is a guided, browser-only self-check for apps built with Lovable, Bolt, Base44 and similar tools. Paste page source, a JS bundle, or response headers you copied from DevTools, then answer a few questions. The page flags likely leaked secrets and missing headers and points you to the matching section of our checklist. For how Lovable behaved in our own builds, see our Lovable review.
Nothing is uploaded. Checking stays in this tab. The page does not fetch your app, does not send the paste to us, and does not call any vendor API. If you paste a real secret, rotate it anyway — treat the paste box like a notepad, not a vault. Copied and downloaded reports are redacted.
This is not a penetration test, a full security audit, a live URL scan, or legal advice. For the full pre-publish list, use the vibe coding security checklist.
Run the self-check
This checker needs JavaScript. Without it, work through the printed checklist instead.
On the live app: right-click → View page source, or DevTools → Sources / Network and copy a script. Do not paste customer data.
DevTools → Network → click the document request → Headers → copy the response header list.
Paste text and/or answer the questions, then run the check.
What it looks for
- Supabase secret keys (
sb_secret_) and legacyservice_roleJWTs versus publishable /anonkeys - Stripe secret and restricted keys (
sk_live_,sk_test_,rk_…) versus publishablepk_keys - Common API-token prefixes such as
sk-proj-,sk-ant-, GitHubghp_/github_pat_, andAKIAAWS IDs - PEM private keys and Firebase-style web configs (usually public, but worth restricting)
- Public storage URL hints and missing security headers in a header paste
Publishable keys are flagged as information, not as “you leaked a master key.” A clean result does not mean the app is safe.
Want us to scan a public URL instead?
This page does not fetch a URL you type in. Browsers block a WordPress page from reading most other sites. To check a live app, copy the page source or response headers from your browser’s DevTools into the boxes above. A hosted URL scanner is not part of this tool.
Related
- Vibe coding security checklist
- Is Lovable secure? Our two-account access-control test
- Add login and a database to an AI app
- What actually broke in our tests
- App builder troubleshooter
- Export and back up AI app code
- Open Lovable · Open Bolt
FAQ
Is my paste uploaded or stored?
No. Checking runs in your browser only. This page does not send the paste to our servers, to an AI service, or to any third party. The report redacts secret-looking strings before you copy or download it.
Is this a penetration test?
No. This is not a penetration test or a full security audit. It cannot fetch your live URL, query your database, or prove that a key is valid. It flags patterns in text you can see and reminds you of checklist items from your answers.
What if it finds a real secret?
Treat it as leaked. Rotate the key at the vendor, remove it from frontend code, and put the new value in a server-side secret form — not in builder chat. Then re-paste the updated source here.
Why didn’t it fetch my app URL?
Browsers block a WordPress page from reading most other sites (CORS). This tool stays fully client-side on purpose. Paste source or headers from DevTools instead.
Does a clean result mean my app is safe?
No. A clean paste only means these patterns were not in the text you provided. You still need row-level security, the two-account test, and the rest of the vibe-coding security checklist.
Pattern references checked Nov 9, 2026. Use this beside the security checklist, not instead of it.