<?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: devops team</title>
    <description>The latest articles on DEV Community by devops team (@devops_team_4eb6408e18284).</description>
    <link>https://dev.to/devops_team_4eb6408e18284</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4031444%2F91f0fc8d-542c-4c60-a090-09ed4bff42bc.png</url>
      <title>DEV Community: devops team</title>
      <link>https://dev.to/devops_team_4eb6408e18284</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/devops_team_4eb6408e18284"/>
    <language>en</language>
    <item>
      <title>A practical checklist for software supply chain security</title>
      <dc:creator>devops team</dc:creator>
      <pubDate>Fri, 17 Jul 2026 06:46:19 +0000</pubDate>
      <link>https://dev.to/devops_team_4eb6408e18284/a-practical-checklist-for-software-supply-chain-security-2nk9</link>
      <guid>https://dev.to/devops_team_4eb6408e18284/a-practical-checklist-for-software-supply-chain-security-2nk9</guid>
      <description>&lt;p&gt;Lately I've been trying to lock down our &lt;strong&gt;software supply chain security&lt;/strong&gt; and it turned into a bigger project than expected. Sharing the checklist we landed on in case it helps someone else.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Know what you ship — SBOM generation
&lt;/h2&gt;

&lt;p&gt;Start with &lt;strong&gt;sbom generation&lt;/strong&gt; for every build. If you can't list your dependencies, you can't secure them.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Secure software dependencies
&lt;/h2&gt;

&lt;p&gt;Add &lt;strong&gt;dependency vulnerability scanning&lt;/strong&gt; to CI so a risky package fails the build early. The goal is to &lt;strong&gt;secure software dependencies&lt;/strong&gt; before they reach production, not after.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Open source license compliance
&lt;/h2&gt;

&lt;p&gt;This is the part everyone forgets. You need &lt;strong&gt;open source license compliance&lt;/strong&gt; checks to &lt;strong&gt;detect open source licensing issues&lt;/strong&gt; before legal does.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Automate it
&lt;/h2&gt;

&lt;p&gt;Manual reviews don't scale. We're looking for an automated tool that handles scanning + SBOM + licensing without needing source code access.&lt;/p&gt;

&lt;p&gt;What are you all using for this? Would love recommendations.&lt;/p&gt;

</description>
      <category>sbomgeneration</category>
      <category>softwaresupplychainsecurity</category>
      <category>opensourcelicensecompliance</category>
    </item>
    <item>
      <title>npm Vulnerabilities Are Growing devnack</title>
      <dc:creator>devops team</dc:creator>
      <pubDate>Thu, 16 Jul 2026 06:00:56 +0000</pubDate>
      <link>https://dev.to/devops_team_4eb6408e18284/npm-vulnerabilities-are-growing-devnack-38b8</link>
      <guid>https://dev.to/devops_team_4eb6408e18284/npm-vulnerabilities-are-growing-devnack-38b8</guid>
      <description>&lt;p&gt;🧩 The Real Problem Isn’t Dependencies — It’s Visibility&lt;/p&gt;

&lt;p&gt;Most developers rely on:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npm outdated
npm audit
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;But let’s be honest—these tools are:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;❌ Noisy
❌ Hard to prioritize
❌ Not decision-friendly
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;They tell you everything, but help you decide nothing.&lt;/p&gt;

&lt;p&gt;You don’t need a list.&lt;br&gt;
You need clarity.&lt;br&gt;
🧠 What This System Does&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Classifies updates (Major / Minor / Patch)
Detects vulnerabilities via OSV.dev
Fetches npm metadata (size, publish date)
Handles git/file/workspace dependencies
Generates CLI + PDF reports
Provides actionable recommendations
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
    </item>
  </channel>
</rss>
