<?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: Aswin </title>
    <description>The latest articles on DEV Community by Aswin  (@ohaswin).</description>
    <link>https://dev.to/ohaswin</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%2F920882%2Fe7c316d8-5d6f-4abc-b629-9584ae590664.jpg</url>
      <title>DEV Community: Aswin </title>
      <link>https://dev.to/ohaswin</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ohaswin"/>
    <language>en</language>
    <item>
      <title>This is why you rewrite Python security tools in Rust: 53MB vs 433MB peak memory, 6.9s vs 62.2s</title>
      <dc:creator>Aswin </dc:creator>
      <pubDate>Sat, 25 Apr 2026 15:11:26 +0000</pubDate>
      <link>https://dev.to/ohaswin/this-is-why-you-rewrite-python-security-tools-in-rust-53mb-vs-433mb-peak-memory-69s-vs-622s-4ea6</link>
      <guid>https://dev.to/ohaswin/this-is-why-you-rewrite-python-security-tools-in-rust-53mb-vs-433mb-peak-memory-69s-vs-622s-4ea6</guid>
      <description>&lt;h2&gt;
  
  
  Your Python security tool is slowing down your pipeline. Here's what I built instead.
&lt;/h2&gt;

&lt;p&gt;I've been working on &lt;a href="https://github.com/ohaswin/pyscan" rel="noopener noreferrer"&gt;Pyscan&lt;/a&gt; on and off for 3 years now. The first version took 6 minutes to scan 200 dependencies. Today it scans 1000+ in less than 5 seconds.&lt;/p&gt;

&lt;p&gt;Here's what it looks like against the tools you're probably already using:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Execution Time&lt;/th&gt;
&lt;th&gt;Peak Memory&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Pyscan&lt;/td&gt;
&lt;td&gt;6.9s&lt;/td&gt;
&lt;td&gt;53MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;pip-audit&lt;/td&gt;
&lt;td&gt;62.2s&lt;/td&gt;
&lt;td&gt;433MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Safety&lt;/td&gt;
&lt;td&gt;10.4s&lt;/td&gt;
&lt;td&gt;320MB&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  The actual problem
&lt;/h2&gt;

&lt;p&gt;Devs get rid of slower security tools to get CI/CD done faster. Which makes sense because nobody wants to babysit a 60 second scan on every push. But that's how vulnerable dependencies sit unpatched for months.&lt;/p&gt;

&lt;p&gt;Memory is very important in CI/CD servers and will significantly affect your budget. Pyscan stays flat at ~53MB whether you're scanning 15 deps or 700+.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Pyscan does
&lt;/h2&gt;

&lt;p&gt;Pyscan automatically traverses your Python project, extracts dependencies across whatever packaging format you use (uv, poetry, PDM, Flit, requirements.txt, CycloneDX and SPDX SBOMs, even raw source files) and cross-references them against the &lt;a href="https://osv.dev/" rel="noopener noreferrer"&gt;Open Source Vulnerabilities (OSV) database&lt;/a&gt; in a single async batch request.&lt;/p&gt;

&lt;p&gt;That last part is why it's fast. Traditional tools query OSV per dependency, serially. Pyscan sends one request for everything. &lt;strong&gt;Runtime scales with vulnerabilities found, not dependency count.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The latest release added:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SBOM Native Support:&lt;/strong&gt; Pyscan now natively parses CycloneDX (&lt;code&gt;bom.json&lt;/code&gt;) and SPDX (&lt;code&gt;spdx.json&lt;/code&gt;) files&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reachability Heuristics:&lt;/strong&gt; It scans your source to find where you're actually importing the vulnerable packages and highlights them in the output&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  One honest thing
&lt;/h2&gt;

&lt;p&gt;Pyscan is on-par with &lt;code&gt;uv audit&lt;/code&gt;, sometimes faster. If you already use &lt;code&gt;uv&lt;/code&gt; you don't need Pyscan at all. Pretty cool since &lt;code&gt;uv&lt;/code&gt; is Rust-based as well.&lt;/p&gt;

&lt;h2&gt;
  
  
  Installation
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# via pipx (recommended)&lt;/span&gt;
pipx &lt;span class="nb"&gt;install &lt;/span&gt;pyscan-rs

&lt;span class="c"&gt;# via pip&lt;/span&gt;
pip &lt;span class="nb"&gt;install &lt;/span&gt;pyscan-rs

&lt;span class="c"&gt;# via cargo&lt;/span&gt;
cargo &lt;span class="nb"&gt;install &lt;/span&gt;pyscan
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It's been featured on the Real Python Podcast and has 60,000+ combined downloads across PyPI and crates.io. Still maintained by one broke college student between classes. Still free, still open source.&lt;/p&gt;

&lt;p&gt;In upcoming releases I'll be improving QoL for CI/CD users and trying to see if I can make it faster than &lt;code&gt;uv&lt;/code&gt; while adding some interesting new features.&lt;/p&gt;

&lt;p&gt;Would love feedback and happy to answer questions about the internals! &lt;a href="https://github.com/ohaswin/pyscan" rel="noopener noreferrer"&gt;GitHub repo here&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>python</category>
      <category>devops</category>
      <category>cybersecurity</category>
      <category>rust</category>
    </item>
  </channel>
</rss>
