Integrate the CycloneDX Yarn plugin with Vulnesis. Generate a CycloneDX SBOM from your Yarn Berry workspace, then upload to Vulnesis for JavaScript supply-chain analysis.
Install & scan
$ # Zero-install via yarn dlx (Yarn Berry v3/v4) yarn dlx -q @cyclonedx/yarn-plugin-cyclonedx --help # Or install the plugin permanently yarn plugin import https://github.com/CycloneDX/cyclonedx-node-yarn/releases/latest/download/yarn-plugin-cyclonedx.cjs $ yarn dlx -q @cyclonedx/yarn-plugin-cyclonedx --output-format JSON --output-file bom.json
Run Yarn CycloneDX in CI
Scan on every push and upload the report as a workflow artifact:
- name: Enable Corepack
run: corepack enable
- name: Install dependencies
run: yarn install --immutable
- name: Generate CycloneDX SBOM
run: yarn dlx -q @cyclonedx/yarn-plugin-cyclonedx --omit dev --output-format JSON --output-file bom.json
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: yarn-cyclonedx
path: bom.json
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under Yarn CycloneDX'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 Yarn CycloneDX. Keep running it. Vulnesis sits on top of Yarn CycloneDX (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Yarn CycloneDX is strongest at its core category and also carries features in SCA, just as Vulnesis spans categories.
| Capability | Vulnesis | Yarn CycloneDX |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ~ Produces the accurate component inventory SCA depends on, 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 | ✗ |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✓ Core: generates CycloneDX 1.2-1.7 component/dependency inventory from Yarn Berry workspaces |
| 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 Yarn CycloneDX does well
- Purpose-built for Yarn Berry (v3/v4) resolution, producing accurate SBOMs where npm-focused tools miss Plug'n'Play / non-node_modules layouts
- Emits standards-compliant CycloneDX 1.2 through 1.7 in JSON or XML, with a selectable spec version
- Recursively resolves workspace dependencies and distinguishes production vs development components
- Reproducible-output option for deterministic, diffable SBOMs in CI attestation pipelines
Where Vulnesis adds to it: The Yarn plugin builds an accurate CycloneDX inventory but stops there, no vuln matching, VEX, or prioritisation. Vulnesis ingests its SBOM (and authors its own CycloneDX 1.7 + SPDX 2.3), then adds SCA vuln matching, exploit-intel prioritisation, reachability, immutable versioned VEX, and cross-scanner dedup across the whole toolchain. It consumes this SBOM as an input, complementing Yarn-native generation.
No migration, no rip-and-replace. Yarn CycloneDX 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 Yarn CycloneDX results in Vulnesis
Upload Yarn CycloneDX 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.