Integrate DISTRO2SBOM with Vulnetix. Generate SPDX or CycloneDX SBOMs from the installed packages on Linux (RPM/DEB), Windows, or FreeBSD systems. Ideal for OS-level supply chain visibility.
Install & scan
$ # Recommended - run without global install uv run --with distro2sbom distro2sbom --version # Install globally with pip pip install distro2sbom $ # Auto-detect distribution and generate CycloneDX SBOM uv run --with distro2sbom distro2sbom --distro auto --system --sbom cyclonedx --format json -o distro-sbom.cdx.json # Generate SPDX SBOM uv run --with distro2sbom distro2sbom --distro auto --system --sbom spdx --format json -o distro-sbom.spdx.json
Run DISTRO2SBOM in CI
Scan on every push and upload the report as a workflow artifact:
- name: Generate OS package SBOM
run: |
pip install distro2sbom
distro2sbom --distro auto --system --sbom cyclonedx --format json -o distro-sbom.cdx.json
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: distro2sbom
path: distro-sbom.cdx.json
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnetix, recorded under DISTRO2SBOM's own name and version. Written once per workflow, however many scanners you run:
publish:
name: Publish to Vulnetix
runs-on: ubuntu-latest
needs: [scan] # every scanner job, or its report is never published
if: always() # or one failing scanner suppresses all the others
permissions:
contents: read
actions: read # required to list the run's artifacts
env:
VULNETIX_ORG_ID: ${{ secrets.VULNETIX_ORG_ID }}
VULNETIX_API_KEY: ${{ secrets.VULNETIX_API_KEY }}
steps:
- uses: actions/checkout@v5
- name: Install Vulnetix CLI
run: |
curl -fsSL https://cli.vulnetix.com/install.sh | sh -s -- --install-dir "$HOME/.local/bin"
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
- name: Publish scanner reports
env:
GITHUB_TOKEN: ${{ github.token }}
run: vulnetix gha upload --org-id "$VULNETIX_ORG_ID" --jsonAfter the run, vulnetix gha status reports what was actually recorded.
How Vulnetix compares: better together
Vulnetix does not replace DISTRO2SBOM. Keep running it. Vulnetix sits on top of DISTRO2SBOM (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
DISTRO2SBOM is strongest at its core category and also carries features in License Compliance, just as Vulnetix spans categories.
| Capability | Vulnetix | DISTRO2SBOM |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✗ |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ~ Maps package license data to SPDX identifiers via a synonym set where the package manager exposes it; no policy/conflict engine. |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✓ Generates SPDX (tag-value/JSON) and CycloneDX from OS package inventory across Debian, RPM, Windows, FreeBSD; auto-detects distro. |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25+ registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ✗ |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✗ |
| The Vulnetix orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✗ |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnetix LEV | ✗ |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ✗ |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ✗ |
| End-of-life policy | ✓ Flags/blocks past-EOL runtimes & packages | ✗ |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What DISTRO2SBOM does well
- Generates OS-level SBOMs from native package managers (dpkg, rpm, Windows, FreeBSD pkg) that source-code SBOM tools miss
- Enumerates system-wide installed packages plus per-application inventory, filling the host/base-image visibility gap
- Emits both SPDX (tag-value/JSON) and CycloneDX with auto-generated purl and CPE references
- Uses a synonym set to map discovered licenses to SPDX identifiers for downstream compliance use
Where Vulnetix adds to it: distro2sbom is a focused OS-inventory SBOM generator with no vuln scanning, dedup, prioritisation, or VEX. Vulnetix consumes its CycloneDX/SPDX output as one input among many, then adds SCA correlation (40+ ecosystems), exploit-intel prioritisation (EPSS/KEV/ESS/LEV), reachability, versioned VEX, and autofix. Better together: distro2sbom captures the host/base-image layer, Vulnetix turns that inventory into a prioritised, remediable queue.
No migration, no rip-and-replace. DISTRO2SBOM keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise DISTRO2SBOM results in Vulnetix
Upload DISTRO2SBOM CycloneDX, SPDX output to the Vulnetix platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.