ops-docker — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ops-docker (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Dockerfile syntax, Compose schema and image-publish flows drift on each release and are canonical at:
RUN addgroup -S app && adduser -S app -G app && USER app — never run app code as root inside the container, even if "it's just a sandbox"..git/ or node_modules/ in the build context bloats images by hundreds of MB and leaks secrets. The .dockerignore rules mirror your .gitignore plus build artifacts.node:20-alpine, not node:latest or bare node:20): floating tags break reproducibility; SHA pinning is overkill for most apps but worth it for security-critical builds.COPY .env or hardcode credentials in ENV. Use BuildKit secrets (--mount=type=secret) or runtime-injected env vars from the orchestrator./ops:ops-deploy — deployment checklist consumes the built image/ops:ops-database — Compose patterns for DB services (depends_on: { condition: service_healthy })qa-security — image scanning gate (Snyk/Trivy) before pushops-ci — Hadolint + image scan as CI steps~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.