# Hullscan

> Use when auditing the build and deploy files of a repo in one pass: Dockerfile, docker-compose, and later Kubernetes YAML and Terraform, plus a secret and dependency sweep of the same tree so nothing slips between tools.

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

---


# hullscan: build and config pass

## job
check how the app is built and shipped (containers, compose, infra files), and run the secret and dependency checks over the same tree so the report has no gaps between file types.

## gap it targets
- evidence (fixture): in our fixture run, a popular all-in-one scanner found three Dockerfile issues (runs as root, no healthcheck, secret in `ENV`) but no secret in `app.py`, and did not scan the lockfile-less `package.json`.
- not yet measured, but checkable: the fixture's `FROM python:3.7` is past end of life. this skill checks base images against public end-of-life data.

## inputs
- a repo path.

## method
1. find `Dockerfile*`, `*.dockerfile`, `docker-compose*.y*ml`, `compose*.y*ml`. note k8s and terraform files as "v2 and v3 coverage, read but not scored".
2. Dockerfile checks, written by us:
   - final stage runs as root: no `USER`, or last `USER` is `root` or `0`
   - no `HEALTHCHECK`
   - secret-like names or values in `ENV` or `ARG`
   - base image tag missing or `latest`; base image past end of life (look up the language or distro version on endoflife.date and cite it)
   - `ADD` from a URL; `curl ... | sh` in `RUN`
   - `COPY . ` with no `.dockerignore`, which can ship `.env` and `.git`
3. compose checks: `privileged: true`, host network, docker socket mounted, secrets in `environment:`, ports bound to `0.0.0.0` for databases.
4. run the `grainseek` method over every file, not only config files.
5. run the `depfathom` method over every manifest.
6. merge: a secret in a Dockerfile `ENV` is one finding with two angles (secret and misconfig), not two.

## what counts as a finding
- a config line that weakens isolation, leaks a secret, or ships a known-bad base, plus everything grainseek and depfathom find.

## output
```json
{"command":"hullscan","rule_id":"ks.docker.eol-base-image","kind":"misconfig","severity":"medium","confidence":"high","cwe":["CWE-1104"],"location":{"path":"Dockerfile","start_line":2},"evidence":"python:3.7, end of life per endoflife.date","sources":["hullscan"],"status":"open"}
```

## today vs later
- today: read the files, `rg`, and any Dockerfile or IaC linter already installed, then fill the gaps above.
- once the keelsec engine exists: `keelsec hullscan <path> --format json` runs all three checks and merges.

## stop and scope
- read only. never build or run the image.

