sbom-tool

Generate SBOMs for build artifacts and source repositories

microsoft/sbom-tool · SBOM Generation · scanned v4.1.5 (released 2025-12-15) · commit c83b43dee2dd · last scan 2026-11-02

The scan method changed on 2026-11-02. npm development dependencies and npm-shrinkwrap.json are now scanned; matches on GitHub Actions referenced by a moving tag and on npm packages the repository defines itself are no longer counted; directories such as integration-tests and test-fixtures are excluded as fixtures. Most differences from the previous week below come from that change, not from the projects. Details.

Changes since last week

no change.

Known vulnerabilities

No known advisories matched the declared dependencies.

Second opinion: OSV-Scanner

OSV-Scanner found 0 advisories in the same files; 0 of Grype's matches are confirmed by it (marked ✓ above). 0 advisories were reported only by OSV-Scanner.

Release integrity

Verdict: no checksums or signatures for sbom-tool-linux-x64. The download matches GitHub's recorded digest.

• Checksums file: no
• Signatures: no
• SLSA provenance: no
• SBOM published with the release: yes

Verified means a signature, provenance, or attestation was checked against an identity in microsoft/sbom-tool's own GitHub Actions workflows.

Repository security (OpenSSF Scorecard)

No Scorecard result yet (the project is not in the OpenSSF public dataset; the Scorecard CLI fallback was skipped because this shard's weekly budget was used). Results are added as the weekly budget allows.

GitHub Actions workflow audit (zizmor)

2 potential issues in 5 workflow files at this release: 2 high, 0 medium, 0 low severity (medium or high confidence only). Each is a pattern to review, not a confirmed vulnerability.

Dependencies (9)

By ecosystem: github 9.

Licenses (as declared in the SBOM): unknown 9.

History

SBOM minimum elements

Scored by sbomlyze on the generated source SBOM. A source SBOM usually lacks supplier and hash data, so these scores mostly reflect what the project's manifests declare.

Evidence

Downloads for this week: CycloneDX SBOM · Grype report

Permanent copy of the raw SBOM, Grype, OSV-Scanner, and govulncheck output and release checks: release report-2026-11-02, folder supply-chain-shard-*/microsoft__sbom-tool/.

Full JSON for this project · Atom feed of weekly changes

Badges

shields.io endpoints refreshed with each weekly scan. They report this week's result for the latest release, nothing more.

[![release verification](https://img.shields.io/endpoint?url=https%3A%2F%2Frezmoss.github.io%2Fawesome-security-pipeline%2Fbadges%2Fmicrosoft%2Fsbom-tool%2Frelease.json)](https://rezmoss.github.io/awesome-security-pipeline/projects/microsoft/sbom-tool/index.html)

How this report is made

Every Sunday a GitHub Actions workflow resolves each catalog tool to its latest release and runs the checks below. Every tool is installed from its own latest release and verified against its published checksum or digest. Nothing from the scanned projects is built or executed; release binaries are analyzed as files.