Free · Client-side · No login
Dockerfile Security Linter
Find risky build patterns and review practical fixes before building your container image.
Quick answer
A Dockerfile security linter reviews build instructions for risky patterns before you build an image. Paste your file to check the final runtime user, base image references, possible secret variables and command patterns. Findings include line numbers, severity and fix examples. Processing runs locally, without building or uploading the file.
What this checks
Runtime root users, latest or untagged images, missing digest pins, ADD usage, potential secret variables, download-to-shell pipelines, APT hygiene, sudo, SSH, world-writable permissions, missing health checks, broad COPY and elevated-access patterns.
It handles comments, parser directives, continuations and stage inheritance. Shell logic, external image settings, build targets and .dockerignore contents remain outside this review. A finding is a prompt for review, not proof of exploitability.
Sources: Docker build guidance, Dockerfile reference and build secrets. Verified November 16, 2026. Rule links identify equivalent Hadolint guidance; no CIS compliance claim is made.
Continue your security review
Frequently asked questions
Does the linter upload or execute my Dockerfile?
No. Analysis runs in your browser. It does not execute commands, build images, download base images or send the pasted file to a server. The input and results area is masked from session recording.
Does this understand multi-stage Dockerfiles?
Yes. It parses FROM stages, named stage inheritance and the final runtime USER and HEALTHCHECK. Checks on build commands still apply to earlier stages. It cannot resolve external image metadata, build arguments or the target stage selected by your build command.
Why flag an image that has no USER instruction?
The final stage has no known non-root user in the pasted file. An external base image may already define a user. Inspect its metadata and set an explicit unprivileged runtime user where appropriate.
Is ADD always unsafe?
No. ADD supports remote retrieval and local archive extraction. The checker asks you to review remote sources and suggests COPY for ordinary local files. Archive handling and checksum verification need context.
Is this a replacement for Hadolint or an image scanner?
No. This is a focused heuristic review, not the Hadolint engine or a dependency vulnerability scan. Equivalent Hadolint rule IDs link to their verified wiki pages. Run your normal build checks and scan the resulting image too.