Generating an SBOM for Java / Kotlin (Gradle)

The step below writes a CycloneDX JSON file in your own pipeline. The CRA Desk scan reads that file and turns it into a readiness report - it never generates one for you.

Add to build.gradle:

plugins {
  id 'org.cyclonedx.bom' version '1.10.0'
}

Run in CI:

./gradlew cyclonedxBom

Produces:: build/reports/bom.json
Format:: CycloneDX JSON

Generator documentation

The whole CI job

GitHub Actions

- uses: actions/checkout@v4
- run: ./gradlew cyclonedxBom
- uses: mmalinowski/cradesk-action@v1
  with:
    sbom-path: build/reports/bom.json

GitLab CI/CD

generate-sbom:
  script:
    - ./gradlew cyclonedxBom

include:
  - component: gitlab.com/cradesk/scan/readiness@1
    inputs:
      sbom_path: build/reports/bom.json

Only the first step changes with your stack - the CRA Desk step after it is identical everywhere.

What goes wrong here

The plugin writes into the module that applies it, so in a multi-project build apply it to the root project or point sbom-path at the module you actually ship.

What CRA Desk does with the result

Components from this build carry pkg:maven package URLs, which the watch matches against OSV's Maven advisories when the SBOM arrives and again as new advisories land. Matching runs on every plan; e-mail alerts and the full match list are what a paid plan adds.

A generator that runs is not the same as coverage. Components with no purl, no version, or from an ecosystem outside the nine we watch are counted as gaps in every report rather than reported as clean.

What we match, and what we deliberately do not Scope classifier