Why we renamed SeeBOM to BOMHort

Why the project moved from SeeBOM to BOMHort, and what changes for users.

What changed

The project name is now BOMHort (formerly known as SeeBOM).

The rename only affects branding and repository naming. The mission and technical direction stay the same: Kubernetes-native SBOM ingestion, enrichment, visualization, and governance.

Why we renamed

The name SeeBOM served us well, but it created confusion: spoken out loud, it sounds very similar to CBOM (Cryptography Bill of Materials).

In the xBOM ecosystem, names like CBOM usually refer to BOM document types, not to tools. Ahead of OpenSSF sandbox intake, we wanted a project name that is clearly identifiable as a platform.

Why “BOMHort”

Hort comes from Old High German and means a guarded treasure hoard.

That maps to the core purpose of the platform: BOMHort is where SBOM data is collected, enriched, organized, and made available for decisions.

Naming journey (short version)

We ran 19 rounds of naming research and evaluated 321 candidates across domains, developer ecosystems, and trademark checks.

Many names were eliminated due to conflicts or ambiguity. BOMHort was the first option that was distinctive, available, and aligned with the project purpose.

What stays the same

  • Same team and maintainership
  • Same architecture and deployment model
  • Same focus on SBOM verification and governance
  • Same commitment to open development

Migration notes

  • GitHub repository: https://github.com/seebom-labs/BOMHort
  • Existing docs and references are being updated from SeeBOM to BOMHort.
  • Runtime behavior and APIs are unchanged by this rename.