|
+2.2.3 SBOM Open-source Tooling Landscape |
2.2.3 SBOM Open-source Tooling LandscapeIntegration and automation are only possible when supported by the necessary tool stack. Based on the SBOM Adoption State of Play 2026, 33% of the organisations rely on open-source tools, thus Table 4 identifies open-source tools that could be integrated into a CI/CD pipeline to support the end-to-end SBOM lifecycle for both CycloneDX and SPDX formats. The tools are categorised based on the SBOM lifecycle phases and should not be considered as an exhaustive, but rather than an indicative list to support the purpose of this document. The following table demonstrates that while some tools are format-agnostic and can support both SBOM formats, certain stages like SBOM generation, schema validation, and/or consumption require format-specific tooling.
scorecard (eBAY)
spdx-maven-plugin, spdx/tools-python, spdx/tools-java, spdx/tools-golang, yocto (enabled by default in poky), linux (make spdx), zephyr (west spdx), kubernetes-sigs/bom, GitHub SBOM, Microsoft sbom-tool (.NET), Syft, Trivy, ORT, SBOMit Table 4 - Open-source SBOM Tool Stack The fragmentation of SBOM formats poses a significant challenge to the implementation and tooling landscape. Tooling exists for seamless conversion between the formats, such as OpenSSF's (15) Protobom. 1. Visão geral
1.1 Referências1.2 Requisitos identificados1.3 Regulamentos relacionados2. Requisitos identificados
3. Regulamentos relacionados
|