<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Provenance on Nalar</title>
    <link>https://nalar.dev/tags/provenance/</link>
    <description>Recent content in Provenance on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/provenance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Verify Build Provenance Before Trusting Artifacts</title>
      <link>https://nalar.dev/verify-build-provenance-before-trusting-artifacts/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/verify-build-provenance-before-trusting-artifacts/</guid>
      <description>&lt;p&gt;A release artifact can have the expected filename, version, and download location without being the artifact your release process was supposed to produce. A compromised publishing account, an unexpected build path, or a mistake in release automation can put different bytes in front of users while everything around those bytes still looks familiar.&lt;/p&gt;&#xA;&lt;p&gt;Checking an artifact&amp;rsquo;s hash helps answer whether the bytes changed relative to a known hash. It does not, by itself, answer where that hash came from or whether those bytes were built from the intended source by an approved build process.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
