<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sbom on Open Component Model</title><link>https://ocm.software/tags/sbom/</link><description>Recent content in Sbom on Open Component Model</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 28 Jul 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://ocm.software/tags/sbom/index.xml" rel="self" type="application/rss+xml"/><item><title>Shipping SBOMs with Your Components</title><link>https://ocm.software/blog/2026-07-28-shipping-sboms-with-your-components/</link><pubDate>Tue, 28 Jul 2026 10:00:00 +0200</pubDate><guid>https://ocm.software/blog/2026-07-28-shipping-sboms-with-your-components/</guid><description>&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;OCM already tells you &lt;em&gt;which artifacts&lt;/em&gt; a component delivers: its Software Bill of Delivery. But that does not answer the question a security team actually has: &lt;em&gt;&amp;ldquo;which dependencies are bundled inside those artifacts, and am I affected by this vulnerability?&amp;rdquo;&lt;/em&gt; Knowing a component ships an OCI image and a CLI binary as a resource does not tell anything about the packages and libraries buried inside that resource.&lt;/p&gt;</description></item></channel></rss>