Container images

A lockfile lists your libraries, not the OpenSSL, glibc or curl that ship in your image. Give the CLI an SBOM of the image and it looks up every package in it, system packages included.

Write the SBOM

An SBOM (software bill of materials) is the list of the packages of an image or a project. stackalarm does not write it: the tools that read images already do it well. It reads CycloneDX and SPDX 2, in JSON.

trivy
trivy image --format cyclonedx --output image.cdx.json ghcr.io/acme/app:latest
syft
syft ghcr.io/acme/app:latest -o cyclonedx-json=image.cdx.json
Docker
docker sbom --format cyclonedx-json -o image.cdx.json ghcr.io/acme/app:latest

Scan the image you deploy, not only the base image of the FROM line: what the Dockerfile installs on top is part of it.

Check it

stackalarm news --sbom image.cdx.json --format summary
What comes back
2026-11-05 | advisory | osv-alpine | 8.1 | [high] musl: musl libc before 1.2.7, when an untrusted regular expression is used with regcomp… (CVE-2026-107891) | https://osv.dev/vulnerability/ALPINE-CVE-2026-107891 | affects musl < 1.2.5-r24 (fixed in 1.2.5-r24) [1.2.5-r21 in use: AFFECTED]
2026-09-29 | advisory | osv-npm | 7.5 | [high] brace-expansion: DoS via uncontrolled recursion on nested brace groups… (CVE-2026-102278) | https://osv.dev/vulnerability/GHSA-qhr7-859c-m2p7 | affects brace-expansion >= 2.0.0, < 2.1.6 (fixed in 2.1.6) [2.0.2 in use: AFFECTED]
TRUNCATED | osv-alpine | 9 more entries left out, those ranked last: the least severe, and in an image those without a fix

Given alone, --sbom lists only the known vulnerabilities of the packages, whatever their date. With tags, a profile or packages, they are added to the usual news. The option is repeatable, one file per image.

OSV.dev is asked about each package in its own ecosystem, and each answer says whether a fixed version exists. CVEs listed in CISA KEV or holding a public exploit are marked, as in the rest of the CLI.

What is covered

PackagesEcosystems
System packagesDebian, Ubuntu, Alpine, Rocky Linux, AlmaLinux, Wolfi, Chainguard
Librariesnpm, Packagist, PyPI, Go, RubyGems, crates.io, Maven, NuGet, Pub, Hex, Swift, GitHub Actions

Anything else is counted in a warning, never dropped in silence: Red Hat and SUSE packages, binaries copied into the image without a package, components without a package URL. A distribution package is looked up under its source package (libssl3 is openssl), which trivy and syft both record.

Read the result

An up-to-date Debian or Ubuntu image always carries dozens of open flaws. Three cases matter:

In the outputMeaningWhat to do
(fixed in …)The distribution ships a fix, and the image holds an older package.Rebuild the image on the current base, or upgrade the package. These come first.
(no fix yet)The distribution has not fixed it.Nothing to install. Look closer when it is exploited, or in a library your application feeds untrusted input to.
[unimportant]Debian judges the flaw is no security issue in its package.Nothing. Listed last.

Each ecosystem shows its 30 most pressing entries: fixable first, then by severity. The output says how many were left out. Ubuntu rates its records with a priority ([medium]) rather than a score.

In the scheduled watch

Write the SBOM in a step before the action and pass its path. The watch then reports a package of the image the day a vulnerability is published for it.

.github/workflows/stackalarm.yml (excerpt)
      - uses: anchore/sbom-action@v0 # or any tool that writes CycloneDX or SPDX
        with:
          image: ghcr.io/acme/app:latest
          format: cyclonedx-json
          output-file: image.cdx.json
      - uses: yoanbernabeu/stackalarm@v0.18.1
        with:
          sbom: image.cdx.json

On GitLab, set the STACKALARM_SBOM variable to the path of a file an earlier job passed as an artifact. Vulnerabilities of packages are advisories: add advisory to fail-on to be woken by them, or keep the default and read them in the report of the next alert.

What is sent

The names and versions of the packages of the SBOM go to OSV.dev (Google), and nothing else from the file. --sbom cannot be combined with --no-osv. See Privacy and security.

Next: Scheduled watch