<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Integrity on Nalar</title>
    <link>https://nalar.dev/tags/integrity/</link>
    <description>Recent content in Integrity on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/integrity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Verify Dependency Integrity Before Installation</title>
      <link>https://nalar.dev/verify-dependency-integrity-before-installation/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/verify-dependency-integrity-before-installation/</guid>
      <description>&lt;p&gt;A dependency declaration such as &lt;code&gt;library = 2.4.1&lt;/code&gt; tells a package manager which release you intend to use. It does not, by itself, prove that the bytes being installed are the same bytes you previously reviewed, tested, or approved.&lt;/p&gt;&#xA;&lt;p&gt;That distinction matters when dependencies cross a trust boundary. Packages may come through registries, mirrors, caches, proxies, build systems, or internal artifact stores. If unexpected bytes are accepted somewhere along that path, a familiar package name and version can create false confidence.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
