We checked 334 public apps built with Lovable, Bolt and v0. 32% had something to fix before launch

We ran a launch check on 334 public GitHub repositories made with Lovable, Bolt and v0, picked at random among those updated in the last two months. It reads the code for what breaks or leaks when an app goes live.

• 32% had at least one thing to fix before launch.
• The median launch score was 80/100.
• 33% were launch-ready (90 or more).

What they'd ship with

• .env file committed: 23% of apps (how to fix it)
• Policies that let anyone change data: 19% of apps (how to fix it)
• Tables without Row Level Security: 7% of apps (how to fix it)
• Supabase admin key used in browser code: 6% of apps (how to fix it)
• Secrets exposed to the browser: 1% of apps (how to fix it)
• Secret keys committed to the repo: 1% of apps (how to fix it)

By tool

• Bolt: 115 apps, median score 90/100, 12% with something to fix before launch
• Lovable: 108 apps, median score 55/100, 79% with something to fix before launch
• v0: 111 apps, median score 85/100, 7% with something to fix before launch

The tools build very different apps, so this compares what their users ship, not the tools themselves.

How it was done

Apps were found by the text each tool puts in the README it exports. Only totals were kept: no repository is named or stored, and the check never reads out a key, only that one is there. A public repository isn't always a launched app, and the check reads code only, so it can't see settings made in a dashboard.

The full results, updated each month, are at launchpad.axonscape.com/report. I work on Launchpad by Axonscape: the same launch check is free for your own app, with no account.