Integrate Chainguard apko with Vulnesis. Build minimal container images from APK packages and automatically generate SPDX SBOMs. Upload the SBOM to Vulnesis for supply chain tracking.
Install & scan
$ # Install via Go go install chainguard.dev/apko@latest # macOS via Homebrew brew install apko $ # Build a container image from apko.yaml # SBOM is automatically generated as sbom-<arch>.spdx.json apko build apko.yaml myapp:latest myapp.tar # Load into Docker docker load < myapp.tar # Upload SBOM to Vulnesis vulnetix upload --file sbom-amd64.spdx.json
Run Chainguard Apko in CI
Scan on every push and upload the report as a workflow artifact:
- name: Install apko
run: go install chainguard.dev/apko@latest
- name: Build image and generate SBOM
run: apko build apko.yaml myapp:${{ github.sha }} myapp.tar
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: chainguard-apko
path: sbom-amd64.spdx.json
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under Chainguard Apko'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 Chainguard Apko. Keep running it. Vulnesis sits on top of Chainguard Apko (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Chainguard Apko is strongest at its core category and also carries features in SBOM Generation, just as Vulnesis spans categories.
| Capability | Vulnesis | Chainguard Apko |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✓ Core: builds minimal reproducible OCI/distroless images from APK packages without a 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 | ✓ Automatically generates a signed SPDX SBOM at build time listing all packages in the image |
| 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 Chainguard Apko does well
- Builds OCI images directly from APK packages via a declarative YAML manifest with no Dockerfile and no build environment, producing minimal/distroless images (often single-digit MB)
- Fully reproducible by default: identical inputs yield bitwise-identical images, with the creation timestamp pinned to epoch so layer digests are stable
- Emits a signed high-fidelity SPDX SBOM at build time from ground truth, rather than reconstructing one after the fact
- Pairs with melange and cosign for keyless OIDC signing, giving an end-to-end reproducible, attestable software factory
Where Vulnesis adds to it: apko is a build tool, not a scanner: it produces clean, minimal images plus an authoritative SPDX SBOM but runs no vulnerability, SCA, malware, secrets or IaC analysis. Vulnesis ingests the apko-produced SBOM and scans/prioritises it, adding cross-scanner dedup, exploit-intel (EPSS/KEV/ESS/LEV), reachability, versioned VEX, autofix, EOL and SSVC. The two are complementary: apko shrinks the attack surface at build time, Vulnesis governs and remediates what remains.
No migration, no rip-and-replace. Chainguard Apko 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 Chainguard Apko results in Vulnesis
Upload Chainguard Apko SPDX, 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.