# Holdsweep

> Use when you have a built container image or an SBOM (CycloneDX or SPDX) and want to know which packages inside it carry known vulnerabilities, without double counting what the source dependency scan already found.

- Skill: `codejunkie99/holdsweep` (Agent Skill)
- Install (CLI): `npx get-skill add codejunkie99/holdsweep`
- Raw SKILL.md: https://api.skillmd.com/api/skills/codejunkie99/holdsweep/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: codejunkie99 (https://skillmd.com/u/codejunkie99)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/codejunkie99/holdsweep

---


# holdsweep: images and SBOMs

## job
list what is actually inside a built image or an SBOM, look up known advisories for each package, and tie results back to source findings so nothing is counted twice.

## gap it targets
- evidence (public record): three of the popular open scanners do overlapping dependency matching, so running more than one double counts. holdsweep marks a finding as "already reported by depfathom" when the same package and advisory came from a manifest.
- hypothesis: reading SBOMs from any generator, and OS packages and language packages in one list, is more useful than tying to one SBOM tool. not measured.

## inputs
- an image the user built or owns (local name, or a `docker save` tarball), or an SBOM file.

## method
1. get a package list:
   - SBOM: parse CycloneDX `components` or SPDX `packages` with name, version, and purl.
   - image: if an SBOM or image scanner is installed, use it to produce an SBOM. if not, `docker save` and read `/var/lib/dpkg/status`, `/lib/apk/db/installed`, `/var/lib/rpm` hints, and language `site-packages` and `node_modules` metadata inside layers.
2. map each to an OSV ecosystem (Debian, Alpine, PyPI, npm, and so on) and query OSV as in depfathom.
3. drop advisories whose fixed version is lower than the installed one.
4. compare with any depfathom results for the same repo: same package plus same advisory group becomes one finding with both sources.
5. note the base image and its end-of-life status.

## what counts as a finding
- a package in the image or SBOM inside an advisory's affected range.

## output
```json
{"command":"holdsweep","rule_id":"ks.image.known-advisory","kind":"image","severity":"high","confidence":"medium","package":{"ecosystem":"Debian:12","name":"openssl","version":"3.0.11-1"},"aliases":["CVE-..."],"target":{"image":"myapp:staging"},"sources":["holdsweep","depfathom"],"status":"open"}
```

## today vs later
- today: whatever SBOM or image tool is installed, plus OSV lookups and your own merge.
- once the keelsec engine exists: `keelsec holdsweep <image|sbom> --format json`.

## stop and scope
- only images the user built or owns. do not pull and scan third-party images unless the user names them.
- never run the container.

