<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dependency on Commentary of Takao</title><link>https://takao.blog/en/tags/dependency/</link><description>Recent content in Dependency on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/dependency/index.xml" rel="self" type="application/rss+xml"/><item><title>Auditing NPM Dependencies: Snyk and automated patch management</title><link>https://takao.blog/en/web/security-dependency-vulnerabilities-npm-audit/</link><pubDate>Sat, 15 Nov 2025 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/security-dependency-vulnerabilities-npm-audit/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Auditing NPM Dependencies: Snyk and automated patch management" /&gt;&lt;h2 id="the-supply-chain-problem"&gt;The Supply Chain Problem
&lt;/h2&gt;&lt;p&gt;Modern JavaScript applications ship tens of thousands of transitive dependencies. Each one is a potential attack vector. The &lt;strong&gt;event-stream&lt;/strong&gt; incident (2018), where a malicious package was injected into a popular dependency, demonstrated that vulnerabilities can come from anywhere in the tree. Relying solely on manual review is impossible at this scale.&lt;/p&gt;
&lt;p&gt;Automated tooling is the only practical defense.&lt;/p&gt;
&lt;h2 id="npm-audit"&gt;npm audit
&lt;/h2&gt;&lt;p&gt;The built-in &lt;code&gt;npm audit&lt;/code&gt; command compares your dependency tree against a curated database of known vulnerabilities.&lt;/p&gt;</description></item></channel></rss>