<?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: Habeeb Salami</title>
    <description>The latest articles on DEV Community by Habeeb Salami (@habeebsl).</description>
    <link>https://dev.to/habeebsl</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3960071%2F25942482-8d81-4a7e-bce7-0ebb360ae4d2.jpg</url>
      <title>DEV Community: Habeeb Salami</title>
      <link>https://dev.to/habeebsl</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/habeebsl"/>
    <language>en</language>
    <item>
      <title>I scanned my side projects for vulnerabilities. It was humbling.</title>
      <dc:creator>Habeeb Salami</dc:creator>
      <pubDate>Sat, 30 May 2026 14:34:16 +0000</pubDate>
      <link>https://dev.to/habeebsl/i-scanned-my-side-projects-for-vulnerabilities-it-was-humbling-53bb</link>
      <guid>https://dev.to/habeebsl/i-scanned-my-side-projects-for-vulnerabilities-it-was-humbling-53bb</guid>
      <description>&lt;p&gt;I ship small apps fast. Some of them I build mostly with AI tools. And every time I deployed one, the same thought nagged at me: I have no idea if this is secure. I'm not a security person. I don't know what I don't know.&lt;/p&gt;

&lt;p&gt;The existing options didn't fit. Most scanners want to live in your CI pipeline, need access to your repo, or spit out a 40-page report full of jargon that I was never going to read, let alone act on.&lt;/p&gt;

&lt;p&gt;So I built DeploySafe (&lt;a href="https://deploysafe.io" rel="noopener noreferrer"&gt;https://deploysafe.io&lt;/a&gt;). The idea is simple: you paste your live app's URL, and it probes the running app the way someone poking at it would.&lt;/p&gt;

&lt;p&gt;Here is what it checks for right now:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Leaked environment variables and API keys sitting in your JS bundles&lt;/li&gt;
&lt;li&gt;Broken or missing access control on routes that should be protected&lt;/li&gt;
&lt;li&gt;Open redirects&lt;/li&gt;
&lt;li&gt;Missing CSRF protection&lt;/li&gt;
&lt;li&gt;Cookies without secure flags&lt;/li&gt;
&lt;li&gt;Vulnerable dependency versions&lt;/li&gt;
&lt;li&gt;Exposed .git and .env files&lt;/li&gt;
&lt;li&gt;Dangerous HTTP methods left enabled&lt;/li&gt;
&lt;li&gt;Missing security headers&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The part I cared about most: it does not just tell you what is wrong. Every finding comes with three things. A plain-English explanation of how the issue would actually get exploited. A rough estimate of what it would cost you if it did. And a copy-paste prompt written to drop straight into your AI coding tool, so you can fix it in a few minutes instead of researching it for an hour.&lt;/p&gt;

&lt;p&gt;A few technical notes for anyone curious how it works:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It drives a real headless browser (Playwright), so it understands single-page
app routes and behaves like a real session instead of just curling endpoints.&lt;/li&gt;
&lt;li&gt;There is a triage layer that filters raw probe output down to real findings.
Cutting false positives has honestly been most of the work. A scanner that
cries wolf is worse than no scanner.&lt;/li&gt;
&lt;li&gt;You can only scan targets you confirm you own or are authorized to test.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It is free to scan, with a small credit grant when you sign up. The deeper parts (full fix prompts, scanning behind a login) are paid through credit packs. It is a solo project, so I am being upfront about that.&lt;/p&gt;

&lt;p&gt;If you scan something and it flags nonsense, I genuinely want to hear about it. And if there is a check you wish it ran, tell me. GraphQL introspection and subdomain takeover detection are already next on my list.&lt;/p&gt;

&lt;p&gt;You can try it at &lt;a href="https://deploysafe.io" rel="noopener noreferrer"&gt;deploysafe.io&lt;/a&gt;. Would love your feedback.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>devops</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
