Integrate the CycloneDX Python tool with Vulnesis. Generate a CycloneDX SBOM from your Python project using uv or pip, then upload to Vulnesis.
Install & scan
$ # Recommended: run without global install uv run --with cyclonedx-bom cyclonedx-py --help # Or install globally uv tool install cyclonedx-bom # or: pip install cyclonedx-bom $ uv run --with cyclonedx-bom cyclonedx-py environment --output-format JSON --output-file bom.json
Run CycloneDX Python in CI
Scan on every push and upload the report as a workflow artifact:
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.12'
- name: Install dependencies
run: pip install -r requirements.txt
- name: Generate CycloneDX SBOM
run: uv run --with cyclonedx-bom cyclonedx-py environment --output-format JSON --output-file bom.json
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: cyclonedx-python
path: bom.json
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under CycloneDX Python's own name and version. Written once per workflow, however many scanners you run:
publish:
name: Publish to Vulnesis
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 Vulnesis CLI
run: |
curl -fsSL https://cli.vulnes.is/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 Vulnesis compares: better together
Vulnesis does not replace CycloneDX Python. Keep running it. Vulnesis sits on top of CycloneDX Python (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
CycloneDX Python is strongest at its core category and also carries features in License Compliance, SCA, just as Vulnesis spans categories.
| Capability | Vulnesis | CycloneDX Python |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ~ Enumerates installed/transitive Python components, but does no vulnerability matching |
| 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 | ~ Captures per-package license metadata; no copyleft/policy compliance checks |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✓ Core purpose: CycloneDX SBOM (JSON+XML) from pip/Poetry/Pipenv manifests+lockfiles and virtualenvs (PDM/uv/Conda via their venv); no SPDX |
| 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 Vulnesis 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, Vulnesis 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 CycloneDX Python does well
- Broad Python coverage: pip requirements.txt, Poetry and Pipenv (both manifest and lockfile) and live virtual environments natively, with PDM, uv and Conda projects captured through their virtual environments
- Self-described as one of the most accurate/complete Python SBOM generators, targeting OWASP SCVS Level-2 (only external signing missing)
- Emits CycloneDX in JSON and XML with Python-specific property taxonomies (cdx:python/pipenv/poetry) for downstream tooling
- Can inspect the actually-installed environment, so the inventory reflects what is really deployed rather than only declared ranges
Where Vulnesis adds to it: Vulnesis ingests this tool's CycloneDX SBOM and adds the missing layers: vulnerability + malware matching across the Python inventory, cross-scanner dedup, exploit-intel prioritisation (EPSS/KEV/ESS/CWSS/LEV), reachability (tree-sitter + CVEAffected), versioned VEX + audit, EOL policy, SSVC and Safe Harbour autofix, plus normalisation to CycloneDX 1.7 / SPDX 2.3. Better together, cyclonedx-python captures the Python component truth, Vulnesis turns it into a prioritised remediation queue.
No migration, no rip-and-replace. CycloneDX Python keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.
Centralise CycloneDX Python results in Vulnesis
Upload CycloneDX Python CycloneDX output to the Vulnesis 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.