Skip to content

Add Sapper (SBOM graph: which products a CVE reaches, KEV/EPSS) to OSS and Dependency management - #124

Open
Perruer wants to merge 1 commit into
sottlmarek:masterfrom
Perruer:add-sapper
Open

Perruer wants to merge 1 commit into
sottlmarek:masterfrom
Perruer:add-sapper

Conversation

@Perruer

@Perruer Perruer commented Sep 25, 2026

Copy link
Copy Markdown

Adds Sapper to OSS and Dependency management.

  • Tool: Perruer/sapper, Apache-2.0, Go.
  • Why: SBOM generators and scanners answer "what is in this product". Sapper answers the next question for teams that ship many products: which of them a given vulnerability reaches and through which dependency path, with actively exploited (CISA KEV) and likely exploited (EPSS) vulnerabilities first. It reads CycloneDX/SPDX SBOMs, OSV data and OpenVEX, and outputs a table, Markdown or JSON, so it fits into CI reporting.
  • Stars and maturity, honestly: the repository is new (v1.0.0 released on 2026-09-25, few stars yet). It is a maintained continuation of bitbomdev/minefield (733★, archived in August 2025), and keeps its history. CI covers Linux/macOS/Windows, Redis, a Docker end-to-end run, govulncheck, CodeQL and OSV-Scanner.
  • Topic: SBOM consumption and vulnerability triage.

Disclosure: I maintain Sapper.

🤖 Generated with Claude Code

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant