ReARM vs SBOM Manager

ReARM is a release governance platform for organizing software composition, security findings, approvals, and evidence around what ships. It versions SBOMs and XBOMs by product, component, and release, with dependency comparisons across versions and search across a portfolio. Releases can retain HBOMs, VEX, VDR, BOV, SARIF, signatures, attestations, and build metadata for 10+ years. Reliza BEAR adds supplier, copyright, and license metadata to SBOMs. ReARM gathers vulnerabilities, weaknesses, policy violations, and license violations from Dependency-Track and other tools for triage and audit. Release policies can check releases automatically and support manual or automated approvals, recording approver identity, timestamp, and an evidence snapshot in an immutable audit trail. It connects with tools including GitHub Actions, GitLab, Azure DevOps, Jenkins, Slack, Microsoft Teams, Microsoft Sentinel, and Dependency-Track. ReARM Community Edition is self-hosted under AGPL 3.0 and can store and version BOMs without Dependency-Track; vulnerability scanning and policy findings require Dependency-Track or imported VDR files. External deployments require TLS. A free plan is available; paid plans start at $195/mo, and a 60-day trial is listed.

SBOM Manager is a free, MIT-licensed command-line tool for maintaining collections of Software Bills of Materials. It records components used in releases or builds and lets users check whether particular components and versions appear. Search tools include module lookup, project filtering, repository listings, and update-history views. Inputs can be SPDX 2.3 Tag/Value or JSON, CycloneDX 1.4 XML or JSON, CSV, and directory listings. Results can print to the console or go to a file in console or CSV formats. Repository archives can be exported and imported for restoration. The project describes continuous-integration and security-audit use. Vulnerability scanning requires a separately configured scanner that accepts an SPDX Tag/Value file; an example uses cve-bin-tool. The Linux tool requires Python 3.7 or later and installs with pip install sbom-manager. It cannot judge SBOM validity or completeness, or decide whether vulnerabilities require fixes.