<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dependencies on Nalar</title>
    <link>https://nalar.dev/tags/dependencies/</link>
    <description>Recent content in Dependencies on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/dependencies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reduce Software Supply Chain Risk with Dependency Controls</title>
      <link>https://nalar.dev/reduce-software-supply-chain-risk-with-dependency-controls/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/reduce-software-supply-chain-risk-with-dependency-controls/</guid>
      <description>&lt;p&gt;Modern applications routinely execute code downloaded from package registries, container registries, build actions, and language-specific ecosystems. That convenience creates supply chain risk: an attacker does not need to compromise your source repository if they can compromise something your build trusts.&lt;/p&gt;&#xA;&lt;p&gt;No single control eliminates this risk. The practical approach is to reduce unnecessary trust and make dependency changes visible.&lt;/p&gt;&#xA;&lt;h2 id=&#34;treat-dependency-resolution-as-a-security-boundary&#34;&gt;Treat dependency resolution as a security boundary&lt;/h2&gt;&#xA;&lt;p&gt;A manifest may specify broad version ranges, while a lockfile records the exact dependency graph selected for a build.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
