<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Personal-Software on samanl33t/blog</title><link>https://blog.samanl33t.com/tags/personal-software/</link><description>Recent content in Personal-Software on samanl33t/blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://blog.samanl33t.com/tags/personal-software/index.xml" rel="self" type="application/rss+xml"/><item><title>Vulnerability Management in the Era of Personal Software</title><link>https://blog.samanl33t.com/writings/0x0006-vulnerability-management-personal-software/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0300</pubDate><guid>https://blog.samanl33t.com/writings/0x0006-vulnerability-management-personal-software/</guid><description>&lt;p&gt;I build a fair bit of my own software now. A couple of &lt;a href="https://github.com/samanl33t"&gt;open-source security tools&lt;/a&gt;, an app or two, some as vibe-coded side projects like &lt;a href="https://tripsplit.pro"&gt;TripSplit&lt;/a&gt;, and most of the infrastructure I use to deploy them. I&amp;rsquo;ve tried my best to build all of it securely and for the last few years I managed to keep it secure as well myself. That part was never the problem.&lt;/p&gt;</description></item></channel></rss>