<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Getting Started on BOMHort Documentation</title><link>https://docs.bomhort.dev/docs/getting-started/</link><description>Recent content in Getting Started on BOMHort Documentation</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://docs.bomhort.dev/docs/getting-started/index.xml" rel="self" type="application/rss+xml"/><item><title>Why we renamed SeeBOM to BOMHort</title><link>https://docs.bomhort.dev/docs/getting-started/rename/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.bomhort.dev/docs/getting-started/rename/</guid><description>&lt;h2 id="what-changed"&gt;What changed&lt;/h2&gt;
&lt;p&gt;The project name is now &lt;strong&gt;BOMHort&lt;/strong&gt; (formerly known as &lt;strong&gt;SeeBOM&lt;/strong&gt;).&lt;/p&gt;
&lt;p&gt;The rename only affects branding and repository naming. The mission and technical direction stay the same: Kubernetes-native SBOM ingestion, enrichment, visualization, and governance.&lt;/p&gt;
&lt;h2 id="why-we-renamed"&gt;Why we renamed&lt;/h2&gt;
&lt;p&gt;The name &lt;strong&gt;SeeBOM&lt;/strong&gt; served us well, but it created confusion: spoken out loud, it sounds very similar to &lt;strong&gt;CBOM&lt;/strong&gt; (Cryptography Bill of Materials).&lt;/p&gt;
&lt;p&gt;In the xBOM ecosystem, names like CBOM usually refer to &lt;strong&gt;BOM document types&lt;/strong&gt;, not to tools. Ahead of OpenSSF sandbox intake, we wanted a project name that is clearly identifiable as a platform.&lt;/p&gt;</description></item></channel></rss>