<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Axonscape</title>
    <description>The latest articles on DEV Community by Axonscape (@axonscape).</description>
    <link>https://dev.to/axonscape</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211837%2Ffd69f048-2126-452e-a848-37099a9e4c69.png</url>
      <title>DEV Community: Axonscape</title>
      <link>https://dev.to/axonscape</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/axonscape"/>
    <language>en</language>
    <item>
      <title>Razorpay webhook not verified: anyone can fake a payment</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Thu, 19 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/razorpay-webhook-not-verified-anyone-can-fake-a-payment-1kp3</link>
      <guid>https://dev.to/axonscape/razorpay-webhook-not-verified-anyone-can-fake-a-payment-1kp3</guid>
      <description>&lt;p&gt;A Razorpay webhook that doesn't check the X-Razorpay-Signature header acts on any JSON posted to it, so someone can mark an order paid without paying.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;Orders or subscriptions turn paid when nobody paid, or the webhook route accepts any request sent to it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;The webhook route reads the event and updates the database without first proving Razorpay sent it. Razorpay signs each event with the webhook secret you chose in its Dashboard, in the &lt;code&gt;X-Razorpay-Signature&lt;/code&gt; header, and only that signature shows the event is real.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Read the raw request body as text before parsing it: the signature is over the exact bytes Razorpay sent.&lt;/li&gt;
&lt;li&gt;Check it with &lt;code&gt;validateWebhookSignature(rawBody, signature, RAZORPAY_WEBHOOK_SECRET)&lt;/code&gt; from the razorpay package, or compare an HMAC-SHA256 of the raw body, keyed with the secret, to the header. Return 400 when it doesn't match.&lt;/li&gt;
&lt;li&gt;Only then act on &lt;code&gt;payment.captured&lt;/code&gt;, &lt;code&gt;order.paid&lt;/code&gt; and the &lt;code&gt;subscription&lt;/code&gt; events, and make handling the same event twice harmless: Razorpay retries.&lt;/li&gt;
&lt;li&gt;Keep the webhook secret in an environment variable, never in the code.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Make the Razorpay webhook route read the raw request body, verify it against the X-Razorpay-Signature header with validateWebhookSignature and RAZORPAY_WEBHOOK_SECRET, return 400 when verification fails, and only then update the database. Handling the same event twice must not change anything.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/razorpay-webhook-not-verified" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/razorpay-webhook-not-verified&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>database</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>Stripe webhook not verified, or missing</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Sat, 14 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/stripe-webhook-not-verified-or-missing-15on</link>
      <guid>https://dev.to/axonscape/stripe-webhook-not-verified-or-missing-15on</guid>
      <description>&lt;p&gt;A Stripe webhook that doesn't check the signature lets anyone post a fake “payment succeeded”. Without a webhook at all, subscriptions never update when payments fail or are cancelled.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;Subscriptions stay active after a failed payment, or the webhook route acts on any JSON posted to it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;The webhook route skips &lt;code&gt;stripe.webhooks.constructEvent&lt;/code&gt;, the call that proves an event came from Stripe, or no webhook route exists.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Verify every event with &lt;code&gt;stripe.webhooks.constructEvent(rawBody, signature, STRIPE_WEBHOOK_SECRET)&lt;/code&gt; before acting on it. It needs the raw request body, not parsed JSON.&lt;/li&gt;
&lt;li&gt;Handle &lt;code&gt;checkout.session.completed&lt;/code&gt; and the &lt;code&gt;customer.subscription&lt;/code&gt; events, and update your database from them.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Make the Stripe webhook route verify every event with stripe.webhooks.constructEvent using the raw request body and STRIPE_WEBHOOK_SECRET, return 400 when verification fails, and update the database on checkout.session.completed and customer.subscription.updated and .deleted.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/stripe-webhook-not-verified" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/stripe-webhook-not-verified&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>database</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>Your app's emails go to spam (SPF, DKIM and DMARC)</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Fri, 13 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/your-apps-emails-go-to-spam-spf-dkim-and-dmarc-47np</link>
      <guid>https://dev.to/axonscape/your-apps-emails-go-to-spam-spf-dkim-and-dmarc-47np</guid>
      <description>&lt;p&gt;Sign-in links and receipts landing in spam usually mean the sending domain isn't set up: no SPF, no DKIM signature, no DMARC record. Gmail and Yahoo now expect all three.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;Magic links, password resets or receipts arrive in spam, or never arrive.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Mail providers check that a domain says which servers may send for it (SPF), that mail is signed (DKIM), and what to do with mail that fails (DMARC). Without them, your app's mail looks like spoofing.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Add your domain in your email provider (Resend → Domains) and create the DNS records it lists: SPF and DKIM.&lt;/li&gt;
&lt;li&gt;Add a DMARC record: a TXT record at &lt;code&gt;_dmarc.yourdomain.com&lt;/code&gt;, e.g. &lt;code&gt;v=DMARC1; p=none; rua=mailto:you@yourdomain.com&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Send from an address on that domain, and give replies somewhere to go (an MX record).&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Make the app send all email from an address on my own domain, read from an EMAIL_FROM environment variable, through Resend, and list the DNS records I need to add.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/app-emails-go-to-spam" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/app-emails-go-to-spam&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>database</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>Move your data off Lovable Cloud to your own Supabase</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Thu, 12 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/move-your-data-off-lovable-cloud-to-your-own-supabase-47cb</link>
      <guid>https://dev.to/axonscape/move-your-data-off-lovable-cloud-to-your-own-supabase-47cb</guid>
      <description>&lt;p&gt;An app on Lovable's built-in backend keeps its database on Lovable's cloud. Export it, load it into a Supabase project of your own, and your users keep their passwords.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;Your Supabase project isn't in your own Supabase dashboard, because Lovable created it on Lovable Cloud.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Lovable doesn't move a project to your own backend in one step: the data has to be exported and restored, and storage files, secrets and sign-in settings set up again.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;In Lovable: More → Database → Manage → Settings → Export data, then Export on the Database card. Download it from More → Storage when Lovable emails you, with any files your app keeps there.&lt;/li&gt;
&lt;li&gt;Create a Supabase project of your own (Launchpad's wizard does it when you turn on Database with Supabase) and deploy.&lt;/li&gt;
&lt;li&gt;Load the export: &lt;code&gt;launchpad db restore &amp;lt;the export file&amp;gt;&lt;/code&gt;. The app's tables, policies and user accounts come across, so people keep their passwords.&lt;/li&gt;
&lt;li&gt;Upload the storage files, and set up secrets and sign-in providers in the new project.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;This app is moving from Lovable Cloud to my own Supabase project. Point the Supabase client at environment variables (VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY) instead of the values written into the code, and list every edge function and secret the app uses so I can set them up in the new project.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/move-off-lovable-cloud" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/move-off-lovable-cloud&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>database</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>Bots flooding your sign-up or contact form</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Wed, 11 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/bots-flooding-your-sign-up-or-contact-form-364f</link>
      <guid>https://dev.to/axonscape/bots-flooding-your-sign-up-or-contact-form-364f</guid>
      <description>&lt;p&gt;Public forms with no bot check are the first thing spam bots find. A free, invisible check stops them without annoying real people.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;Fake sign-ups, junk messages, or your email provider's quota used up overnight.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;The form accepts anything posted to it, and scripts post to every form they find.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Add Cloudflare Turnstile (free, usually invisible) to the form.&lt;/li&gt;
&lt;li&gt;Verify its token on the server before saving anything.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Add Cloudflare Turnstile to every public form, and verify the token on the server (with TURNSTILE_SECRET_KEY) before processing the submission.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/forms-flooded-by-bots" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/forms-flooded-by-bots&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>Firebase rules let anyone write, or test mode is expiring</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Tue, 10 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/firebase-rules-let-anyone-write-or-test-mode-is-expiring-90n</link>
      <guid>https://dev.to/axonscape/firebase-rules-let-anyone-write-or-test-mode-is-expiring-90n</guid>
      <description>&lt;p&gt;Firestore in test mode, or rules with allow write: if true, let anyone change or delete your data, and test mode switches everything off on its expiry date.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;firestore.rules&lt;/code&gt; has &lt;code&gt;allow read, write: if true&lt;/code&gt;, or the test-mode rule that opens everything until a date.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Test mode is how Firebase starts a project. It's meant to be replaced before launch, and nothing reminds you.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Require a signed-in user, matched to the document: &lt;code&gt;allow write: if request.auth != null &amp;amp;&amp;amp; request.auth.uid == userId&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Deploy the rules: &lt;code&gt;firebase deploy --only firestore:rules&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Replace the open Firestore security rules with rules that require a signed-in user and only let each user read and write their own documents. Keep public reads only where data is meant to be public.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/firebase-rules-open" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/firebase-rules-open&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>API routes and admin pages anyone can call</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Mon, 09 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/api-routes-and-admin-pages-anyone-can-call-1pmk</link>
      <guid>https://dev.to/axonscape/api-routes-and-admin-pages-anyone-can-call-1pmk</guid>
      <description>&lt;p&gt;Routes and server actions that change data without checking who's signed in, and admin pages hidden only by not linking to them, are open to anyone who finds the address.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;An &lt;code&gt;/api&lt;/code&gt; route or server action writes to the database with no sign-in check, or &lt;code&gt;/admin&lt;/code&gt; opens for anyone who types the address.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;AI tools build the feature first; checking who's asking is a separate step that's easy to leave out, and nothing in a demo shows it's missing.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;At the top of every route and action that changes data, get the signed-in user and stop if there isn't one, or if they don't own what's being changed.&lt;/li&gt;
&lt;li&gt;Protect admin pages in a middleware or the admin layout, checking the user is an admin.&lt;/li&gt;
&lt;li&gt;Public forms (contact, waitlist) are fine without sign-in: give them a bot check instead.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Add an authentication check to every API route and server action that writes data: get the signed-in user, return 401 if there's none and 403 if they don't own the record. Protect every /admin page with a check that the user is an admin, in middleware or the admin layout.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/api-routes-anyone-can-call" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/api-routes-anyone-can-call&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>We checked 210 public apps built with Lovable, Bolt and v0. 20% had something to fix before launch</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Sun, 08 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/we-checked-334-public-apps-built-with-lovable-bolt-and-v0-32-had-something-to-fix-before-launch-4dcd</link>
      <guid>https://dev.to/axonscape/we-checked-334-public-apps-built-with-lovable-bolt-and-v0-32-had-something-to-fix-before-launch-4dcd</guid>
      <description>&lt;p&gt;&lt;em&gt;Updated with the latest monthly run. Earlier versions of this article showed an earlier run's totals; changes to how the check counts are listed in the &lt;a href="https://launchpad.axonscape.com/changelog" rel="noopener noreferrer"&gt;changelog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;We ran a launch check on 210 public GitHub repositories made with Lovable, Bolt and v0, picked at random among those updated since 18 September 2026. It reads the code for what breaks or leaks when an app goes live.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;20%&lt;/strong&gt; had at least one thing to fix before launch.&lt;/li&gt;
&lt;li&gt;The median launch score was &lt;strong&gt;80/100&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;24%&lt;/strong&gt; were launch-ready (90 or more).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What they'd ship with
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Policies that let anyone change data: 12% of apps (&lt;a href="https://launchpad.axonscape.com/fix/supabase-row-level-security" rel="noopener noreferrer"&gt;how to fix it&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;.env file committed: 21% of apps (&lt;a href="https://launchpad.axonscape.com/fix/env-file-committed-to-github" rel="noopener noreferrer"&gt;how to fix it&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Tables without Row Level Security: 4% of apps (&lt;a href="https://launchpad.axonscape.com/fix/supabase-row-level-security" rel="noopener noreferrer"&gt;how to fix it&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Secrets exposed to the browser: 3% of apps (&lt;a href="https://launchpad.axonscape.com/fix/ai-api-key-exposed-in-browser" rel="noopener noreferrer"&gt;how to fix it&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Secret keys committed to the repo: 2% of apps (&lt;a href="https://launchpad.axonscape.com/fix/env-file-committed-to-github" rel="noopener noreferrer"&gt;how to fix it&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Supabase admin key used in browser code: 2% of apps (&lt;a href="https://launchpad.axonscape.com/fix/supabase-service-role-key-in-browser" rel="noopener noreferrer"&gt;how to fix it&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  By tool
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Bolt: 9 apps, too few to compare&lt;/li&gt;
&lt;li&gt;Lovable: 85 apps, median score 70/100, 36% with something to fix before launch&lt;/li&gt;
&lt;li&gt;v0: 116 apps, median score 85/100, 7% with something to fix before launch&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The tools build very different apps, so this compares what their users ship, not the tools themselves.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it was done
&lt;/h2&gt;

&lt;p&gt;Apps were found by the text each tool puts in the README it exports, and counted only where the check itself recognised the tool in the repository. 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.&lt;/p&gt;




&lt;p&gt;The full results, updated each month, are at &lt;a href="https://launchpad.axonscape.com/report" rel="noopener noreferrer"&gt;launchpad.axonscape.com/report&lt;/a&gt;. I work on Launchpad by Axonscape: the same &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;launch check&lt;/a&gt; is free for your own app, with no account.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>security</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>.env file and API keys committed to GitHub</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Sat, 07 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/env-file-and-api-keys-committed-to-github-4nl0</link>
      <guid>https://dev.to/axonscape/env-file-and-api-keys-committed-to-github-4nl0</guid>
      <description>&lt;p&gt;A .env file exported with the code puts every key in it where anyone with access to the repository can read them, and deleting the file doesn't remove them from git history.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;The repository has a &lt;code&gt;.env&lt;/code&gt; file, or keys written straight into the code (&lt;code&gt;sk_live_…&lt;/code&gt;, &lt;code&gt;re_…&lt;/code&gt;, a database URL with its password).&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Some tools export the &lt;code&gt;.env&lt;/code&gt; with the project, and the &lt;code&gt;.gitignore&lt;/code&gt; Vite starts with doesn't cover &lt;code&gt;.env&lt;/code&gt; files. Once committed, a key stays in the history even after the file is deleted.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Revoke and replace every key the file held, in each provider's dashboard.&lt;/li&gt;
&lt;li&gt;Remove the file from git (&lt;code&gt;git rm --cached .env&lt;/code&gt;) and add &lt;code&gt;.env*&lt;/code&gt; to &lt;code&gt;.gitignore&lt;/code&gt; (with &lt;code&gt;!.env.example&lt;/code&gt; if you keep one).&lt;/li&gt;
&lt;li&gt;Set the new values at the host instead.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Remove .env from the repository (keep it locally), add .env* to .gitignore with !.env.example, create a .env.example listing every variable with no values, and make sure no key or password is written in the code. Then list every key I need to revoke and replace.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/env-file-committed-to-github" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/env-file-committed-to-github&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>Anyone can run up your OpenAI bill</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Fri, 06 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/anyone-can-run-up-your-openai-bill-1l6b</link>
      <guid>https://dev.to/axonscape/anyone-can-run-up-your-openai-bill-1l6b</guid>
      <description>&lt;p&gt;An AI endpoint with no sign-in and no rate limit can be called in a loop by a bot or one curious person, and your AI provider bills you for every request.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;Your AI provider's usage spikes overnight, or a route like &lt;code&gt;/api/chat&lt;/code&gt; answers anyone who calls it, as fast as they call.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;The route that calls the model checks neither who's asking nor how often. Scripts find routes like that within days.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Require sign-in for anything that costs money.&lt;/li&gt;
&lt;li&gt;Limit requests per user or per IP, for example with &lt;code&gt;@upstash/ratelimit&lt;/code&gt; and Redis.&lt;/li&gt;
&lt;li&gt;Set a monthly spending cap in the AI provider's dashboard.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Add a rate limit to every API route that calls an AI model: per signed-in user, or per IP for anonymous use (for example @upstash/ratelimit with Upstash Redis), and require sign-in where the feature allows it. Return a clear 429 when the limit is reached.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/ai-bill-rate-limit" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/ai-bill-rate-limit&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>OpenAI or Anthropic API key exposed in the browser</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Thu, 05 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/openai-or-anthropic-api-key-exposed-in-the-browser-5940</link>
      <guid>https://dev.to/axonscape/openai-or-anthropic-api-key-exposed-in-the-browser-5940</guid>
      <description>&lt;p&gt;An AI client created with dangerouslyAllowBrowser, or a key behind a VITE_ or NEXT_PUBLIC_ prefix, puts your API key in the page, where anyone can copy it and spend on your account.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;The OpenAI or Anthropic client is created in a component, with &lt;code&gt;dangerouslyAllowBrowser: true&lt;/code&gt;, or the key is read from &lt;code&gt;VITE_OPENAI_API_KEY&lt;/code&gt; or &lt;code&gt;NEXT_PUBLIC_…&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Anything the browser runs, every visitor can read. A public prefix means the value is bundled into the JavaScript everyone downloads.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Revoke the key in the provider's dashboard now: it has already shipped.&lt;/li&gt;
&lt;li&gt;Call the AI from a server route that holds a new key (without a public prefix).&lt;/li&gt;
&lt;li&gt;Have the browser call that route, and limit how often each user can.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The AI API key is exposed in the browser. Move every AI call to a server-side API route that reads the key from a server-only environment variable (no VITE_ or NEXT_PUBLIC_ prefix), have the browser call that route, and add a per-user rate limit. Then tell me to revoke the old key.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/ai-api-key-exposed-in-browser" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/ai-api-key-exposed-in-browser&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
    <item>
      <title>Supabase service-role key exposed in the browser</title>
      <dc:creator>Axonscape</dc:creator>
      <pubDate>Wed, 04 Nov 2026 09:40:53 +0000</pubDate>
      <link>https://dev.to/axonscape/supabase-service-role-key-exposed-in-the-browser-49ce</link>
      <guid>https://dev.to/axonscape/supabase-service-role-key-exposed-in-the-browser-49ce</guid>
      <description>&lt;p&gt;The service-role key skips every Row Level Security rule. Used in browser code, it's handed to every visitor, who can then read, change or delete your whole database.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you see
&lt;/h2&gt;

&lt;p&gt;Code that runs in the browser creates a Supabase client with &lt;code&gt;SUPABASE_SERVICE_ROLE_KEY&lt;/code&gt; (or a key whose role is &lt;code&gt;service_role&lt;/code&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;AI tools reach for the service-role key when a query is blocked by RLS: it makes the error go away by switching security off. In browser code, the key ships to everyone.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Use the anon key in the browser, and fix the RLS policy that blocked the query instead.&lt;/li&gt;
&lt;li&gt;Keep the service-role key in server code only: an API route, a server action or an edge function.&lt;/li&gt;
&lt;li&gt;Rotate the key in Supabase → Settings → API: it has already shipped.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Or ask your AI tool to fix it
&lt;/h2&gt;

&lt;p&gt;Paste this into Lovable, Bolt, v0, Replit or Cursor:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The Supabase service-role key is used in code that runs in the browser. Move every use of it to server-side code (an API route or edge function), use the anon key in the browser, and make the RLS policies allow what the app needs. Then tell me to rotate the key in Supabase.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;The full page, with the request ready to copy, is at &lt;a href="https://launchpad.axonscape.com/fix/supabase-service-role-key-in-browser" rel="noopener noreferrer"&gt;launchpad.axonscape.com/fix/supabase-service-role-key-in-browser&lt;/a&gt;. I work on Launchpad by Axonscape, which runs a &lt;a href="https://launchpad.axonscape.com/check" rel="noopener noreferrer"&gt;free launch check&lt;/a&gt; for apps built with AI tools: it finds this and the other things that break at launch, from a public GitHub repo or a .zip of the code, and keeps nothing.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
  </channel>
</rss>
