<?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: Jacob</title>
    <description>The latest articles on DEV Community by Jacob (@silex_dev_9ca1ec588f29a86).</description>
    <link>https://dev.to/silex_dev_9ca1ec588f29a86</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%2F3713112%2Feb1e17dd-f9d9-4b8e-a62c-c23dfc6cfb83.jpg</url>
      <title>DEV Community: Jacob</title>
      <link>https://dev.to/silex_dev_9ca1ec588f29a86</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/silex_dev_9ca1ec588f29a86"/>
    <language>en</language>
    <item>
      <title>I built a security scanner specifically for vibe coded apps</title>
      <dc:creator>Jacob</dc:creator>
      <pubDate>Thu, 15 Jan 2026 17:07:52 +0000</pubDate>
      <link>https://dev.to/silex_dev_9ca1ec588f29a86/i-built-a-security-scanner-specifically-for-vibe-coded-apps-2o40</link>
      <guid>https://dev.to/silex_dev_9ca1ec588f29a86/i-built-a-security-scanner-specifically-for-vibe-coded-apps-2o40</guid>
      <description>&lt;p&gt;Last summer I started messing around with Cursor, Bolt, Lovable - the usual suspects. Built a few small projects. Shipped fast. Felt great.&lt;/p&gt;

&lt;p&gt;Then my day job brain kicked in. I'm a security engineer. So I started poking at my own apps.&lt;/p&gt;

&lt;p&gt;Not great.&lt;/p&gt;

&lt;p&gt;Then I started looking at other vibe-coded apps. Worse.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The same issues kept showing up:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Missing Supabase RLS policies&lt;/strong&gt; - This one's everywhere. Your database is basically public. Anyone with the Supabase URL can read/write whatever they want.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Weak or missing HTTP security headers&lt;/strong&gt; - No CSP, no X-Frame-Options, nothing. Low-hanging fruit for attackers.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;No rate limiting&lt;/strong&gt; - Your login page will happily accept 10,000 password attempts per second.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Weak password policies&lt;/strong&gt; - "password123" is perfectly acceptable.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;AI tools are incredible at building features fast. They're not great at thinking about who might try to break those features.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;So I built a scanner specifically for this.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It's an external scan - just paste your URL and it runs. The core scan takes about 5 minutes and is free. Full results are $5.&lt;/p&gt;

&lt;p&gt;I optimized it for the specific patterns and mistakes AI-generated code tends to make. It's not a generic "enterprise security audit" - it's built for people who shipped something with Bolt last weekend and want to know if it's leaking data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;→ &lt;a href="https://vibeappscanner.com" rel="noopener noreferrer"&gt;vibeappscanner.com&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Would love feedback from this community. What security stuff are you worried about with your vibe-coded projects? What would you want a tool like this to check for?&lt;/p&gt;

</description>
      <category>ai</category>
    </item>
  </channel>
</rss>
