Integrate the CycloneDX Maven Plugin with Vulnesis. Generate a CycloneDX SBOM from your Maven project including all dependencies, then upload to Vulnesis.
Install & scan
$ # No separate install required: invoke directly via Maven # Or add to pom.xml for persistent configuration: # <plugin> # <groupId>org.cyclonedx</groupId> # <artifactId>cyclonedx-maven-plugin</artifactId> # <version>2.9.1</version> # </plugin> $ mvn org.cyclonedx:cyclonedx-maven-plugin:makeAggregateBom
Run CycloneDX Maven Plugin in CI
Scan on every push and upload the report as a workflow artifact:
- name: Generate CycloneDX SBOM
run: mvn org.cyclonedx:cyclonedx-maven-plugin:makeAggregateBom -DoutputFormat=json
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: cyclonedx-maven
path: target/bom.json
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under CycloneDX Maven Plugin'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 Maven Plugin. Keep running it. Vulnesis sits on top of CycloneDX Maven Plugin (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
CycloneDX Maven Plugin is strongest at its core category and also carries features in SCA, License Compliance, just as Vulnesis spans categories.
| Capability | Vulnesis | CycloneDX Maven Plugin |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ~ Resolves full direct+transitive Maven dependency tree with purls, but performs no vulnerability matching itself. |
| 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 | ~ Includes per-dependency license metadata from POMs (optional license text via includeLicenseText); no policy or conflict detection. |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✓ Generates CycloneDX XML/JSON (spec version tracks plugin release, e.g. 2.9.x=v1.6) from the resolved Maven dependency graph. |
| 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 Maven Plugin does well
- Official CycloneDX generator for Maven/Java, introspecting the resolved dependency graph for accurate direct + transitive components
- Emits precise pkg:maven purls and full CycloneDX BOM in XML or JSON as a native build step
- makeAggregateBom handles multi-module reactor builds, producing one aggregate plus per-module BOMs
- Captures dependency license metadata (optionally including license text) from POMs
Where Vulnesis adds to it: The CycloneDX Maven plugin is a build-time BOM generator scoped to a single Java/Maven project, no vuln matching, cross-project dedup, prioritisation, or VEX. Vulnesis ingests its CycloneDX output and layers SCA vuln correlation, exploit-intel (EPSS/KEV/ESS/LEV), reachability, license policy, EOL, and versioned VEX across all ecosystems. Better together: the plugin gives Vulnesis an authoritative Maven dependency graph, Vulnesis turns it into a prioritised, remediable finding set.
No migration, no rip-and-replace. CycloneDX Maven Plugin 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 Maven Plugin results in Vulnesis
Upload CycloneDX Maven Plugin 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.
CycloneDX Maven Plugin documentation ↗ · Source repository ↗