<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Supply Chain on remixware.com</title>
    <link>https://remixware.com/tags/supply-chain/</link>
    <description>Recent content in Supply Chain on remixware.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://remixware.com/tags/supply-chain/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remixware Now Fails Pull Requests That Bring In Risky Dependencies</title>
      <link>https://remixware.com/remixware-now-fails-pull-requests-that-bring-in-risky-dependencies/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/remixware-now-fails-pull-requests-that-bring-in-risky-dependencies/</guid>
      <description>&lt;p&gt;A pull request that adds one line to &lt;code&gt;package.json&lt;/code&gt; can add forty packages to the lockfile. Reviewers read the line. Hardly anyone reads the lockfile, and that&amp;rsquo;s where a package nobody chose, or one that runs a script on every developer&amp;rsquo;s machine at install time, gets in.&lt;/p&gt;&#xA;&lt;p&gt;Remixware 0.3 adds a second check for that moment. &lt;code&gt;remixware deps&lt;/code&gt; compares the packages your lockfiles name with the ones on your main branch. A new package that isn&amp;rsquo;t on your allow list fails the change, whether you asked for it or another package pulled it in. So does an added or updated package that runs code when it&amp;rsquo;s installed, and, if you let it look online, a recent release by someone who didn&amp;rsquo;t publish or maintain the version before it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
