Knowledge that deliberately breaks every convention it documents.
XBOM stands for eXtreme Bill of Materials. It extends the traditional BOM concept beyond simple component lists into a comprehensive mapping of dependencies, relationships, and hidden connections within complex systems.
Where a standard BOM catalogs parts, an XBOM catalogs everything: software dependencies, supply chain nodes, vulnerability surfaces, environmental impacts, and recursive sub-component trees that go layers deep.
In an era of software supply chain attacks, hardware counterfeiting, and regulatory compliance, understanding the full depth of your materials is not optional. XBOM makes the invisible visible.
Software Bill of Materials. Every library, framework, and dependency mapped with version, license, and known vulnerabilities.
Hardware Bill of Materials. Physical components, chips, boards, and materials traced to origin manufacturers and supply chains.
Cryptographic Bill of Materials. Encryption algorithms, key sizes, certificate chains, and cryptographic protocol dependencies.
Vulnerability Exploitability eXchange. Status documents declaring whether known vulnerabilities actually affect your specific deployment.
Manufacturing Bill of Materials. Production processes, assembly instructions, and manufacturing-specific component variations documented.
SaaS Bill of Materials. Cloud service dependencies, API integrations, data flows, and third-party service components mapped.
Direct dependencies. The libraries you import, the hardware you purchase, the services you subscribe to. This is where most BOMs stop.
Dependencies of dependencies. The npm packages your packages rely on. The sub-components inside your chips. The infrastructure behind your cloud provider.
Build tools, compilers, CI/CD pipelines, development environments. They shape your product but never appear in it. XBOM captures these ghosts.
The operating systems, runtimes, container images, and hardware architectures. The ground your software stands on. XBOM maps the terrain.
Maintainers, contributors, organizations. The humans behind the code. XBOM acknowledges that every component has a human story.
Knowledge doesn't have to be boring.
Structure doesn't have to mean rigid.
Technical doesn't have to mean cold.
A wiki that breaks its own rules
is a wiki that remembers it's alive.