<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Npm on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/npm/</link><description>Recent content in Npm on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Jul 2026 12:56:53 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/npm/index.xml" rel="self" type="application/rss+xml"/><item><title>npm adds publish-time malware scanning and dual-use metadata requirement</title><link>https://curadevops.metacog.co.kr/insights/2026-07-29-npm-publish-time-malware-scanning-and-dual-use-metadata/</link><pubDate>Wed, 29 Jul 2026 12:56:53 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-29-npm-publish-time-malware-scanning-and-dual-use-metadata/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> Teams that publish npm packages via their release pipelines should review the new dual-use metadata requirement to ensure compliance before enforcement begins; no hard deadline surfaced in the item, so schedule this in the next pipeline audit cycle.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> npm&amp;rsquo;s automated publish-time scanning strengthens the ecosystem&amp;rsquo;s supply-chain posture; worth noting as a positive signal when reviewing org-wide software supply-chain policy, but no leadership decision is required now.&lt;/li>
&lt;/ul></description></item></channel></rss>