Integrate the CycloneDX Gradle Plugin with Vulnesis. Generate a CycloneDX SBOM from your Gradle project, then upload to Vulnesis.
Install & scan
$ # Add to build.gradle (Groovy) or build.gradle.kts (Kotlin):
# plugins { id 'org.cyclonedx.bom' version '1.10.0' }
$ ./gradlew cyclonedxBom
Run CycloneDX Gradle Plugin in CI
Scan on every push and upload the report as a workflow artifact:
- name: Generate CycloneDX SBOM
run: ./gradlew cyclonedxBom
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: cyclonedx-gradle
path: build/reports/bom.json
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under CycloneDX Gradle 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 Gradle Plugin. Keep running it. Vulnesis sits on top of CycloneDX Gradle Plugin (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
CycloneDX Gradle Plugin is strongest at its core category and also carries features in License Compliance, SCA, just as Vulnesis spans categories.
| Capability | Vulnesis | CycloneDX Gradle Plugin |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ~ Enumerates full transitive dependency inventory with PURLs, but does 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 | ~ Captures per-component license metadata from POM/Gradle data; no copyleft/policy compliance analysis |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✓ Core purpose: valid CycloneDX 1.6 SBOM (JSON+XML) from Gradle builds; CycloneDX only, no SPDX output |
| 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 Gradle Plugin does well
- Official CycloneDX generator for Gradle/JVM builds, resolves the full direct + transitive dependency graph from Gradle's own resolution engine, so package URLs, hashes and versions match what actually builds
- Emits valid CycloneDX 1.6 in both JSON and XML, and can produce per-project SBOMs or a single consolidated SBOM across a multi-project Gradle build
- Enriches components with license, hash and organizational/build-system metadata captured straight from POM/Gradle metadata
- Zero-config drop-in for the Gradle ecosystem (Java, Kotlin, Groovy, Scala) that fits naturally into existing build pipelines
Where Vulnesis adds to it: Vulnesis ingests the CycloneDX 1.6 SBOM this plugin produces and layers on what it does not do: vulnerability matching, cross-scanner dedup into one queue, exploit-intel prioritisation (EPSS/KEV/ESS/LEV), reachability, license-policy enforcement, immutable versioned VEX and Safe Harbour autofix. It also normalises to CycloneDX 1.7 / SPDX 2.3. Better together, the plugin generates the JVM inventory, Vulnesis turns it into a prioritised, actionable risk queue.
No migration, no rip-and-replace. CycloneDX Gradle 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 Gradle Plugin results in Vulnesis
Upload CycloneDX Gradle 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 Gradle Plugin documentation ↗ · Source repository ↗