Is dockerfile-scan safe to install?

SaferSkills independently audited dockerfile-scan (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/dockerfile-scan/SKILL.md · 1 file

skills/dockerfile-scan/SKILL.md1.9 KB · Markdown

name: dockerfile-scan

description: >-

Scan a Dockerfile for insecure build patterns — running as root, unpinned or

:latest base images, ADD from remote URLs, piping curl/wget into a shell,

hardcoded secrets in ENV/ARG, world-writable chmod 777, and sudo usage. Use

when the user asks to "review my Dockerfile", "is this container image

secure", "lint my Dockerfile for security", or "why does my image run as

root".

license: MIT

Dockerfile Security Scan

Parses a Dockerfile and flags common security and supply-chain problems, each with a concrete fix. Pure text analysis — no Docker daemon, no network, stdlib only.

When to use this skill

"Review this Dockerfile for security issues."
"Is my container running as root?"
"Lint my Dockerfiles before I push them."

What it checks

Base image pinning — missing tag or :latest (docker-no-tag,

docker-latest-tag).

Runs as root — no USER, or final USER is root (docker-root-user).
Remote code execution — curl|wget … | sh (docker-remote-exec).
Remote ADD — ADD http://… without integrity checks

(docker-add-remote).

Hardcoded secrets — ENV/ARG with a secret-looking name and a value

(docker-hardcoded-secret).

Loose permissions — chmod 777 (docker-chmod-777).
sudo usage in RUN (docker-sudo).

How to run it

# Scan one Dockerfile
python skills/dockerfile-scan/scanner.py path/to/Dockerfile

# Scan every Dockerfile under a directory, as JSON
python skills/dockerfile-scan/scanner.py . --json

Exit codes: 0 clean · 1 findings present · 2 usage/IO error.

Recommended workflow for Claude

Run the scan on the file or repo.
Present findings by severity, each with its one-line fix.
Offer a corrected Dockerfile snippet (pinned base image, non-root USER,

COPY instead of remote ADD, secrets moved to runtime).

dockerfile-scan— agent skill

Is dockerfile-scan safe to install?

Dockerfile Security Scan

When to use this skill

What it checks

How to run it

Recommended workflow for Claude

Audit the pieces. Scan the whole. Decide.