What it does
Paste a Dockerfile, a GitHub Actions workflow, a docker-compose file or a .env file. The tool guesses the type (you can also choose it) and lists the settings that are often a problem. Each finding shows the line, a severity (error, warning or info), why it matters and a way to fix it. The whole report can be copied as Markdown, for example for a pull request comment.
What it checks
Dockerfile:
FROMwith no tag or:latest- no
USERline, orUSER rootat the end of the final stage ADDwhereCOPYwould docurlorwgetpiped into a shell- secrets in
ENVandARG EXPOSE 22andsudoapt-get installwithout--no-install-recommendsor without cleaning the package lists (info)- no
HEALTHCHECK(info)
GitHub Actions:
- third-party actions pinned to a tag or branch instead of a full commit SHA
pull_request_targetthat checks out the pull request code- no
permissionsblock, orwrite-all - untrusted
github.event.*text used inside arunscript (script injection) - secrets printed with
echo - a download piped into a shell
docker-compose:
privileged: truenetwork_mode: host- the Docker socket mounted into a container
- database ports published on all interfaces
- plain secrets in
environment
.env:
- duplicate keys
- spaces around
= - unquoted values with spaces or
# - lines that are not
KEY=value, and quotes that never close - values that look like real secrets (checked with the tool's own patterns)
- an
exportprefix (info)
What it cannot catch
- Whether a setting is really a problem for you. A privileged container or a root user is sometimes needed. The tool only points at it.
- Anything outside the file. Included files,
extendsand anchors in other files, build arguments passed on the command line and the contents of the images are not read. - Secrets with no recognisable shape. A secret is found by its name or its format. An ordinary-looking password under a harmless name is not.
- Dynamic or indirect code. Shell written across several variables, code in other scripts and expressions built at run time are not followed.
- Full rule sets. This is a small set of common checks, not a replacement for tools such as hadolint or actionlint, and it does not check that the file is valid for Docker or GitHub.
- Only the first YAML document in a file is checked.
Limits
Input is limited to 100,000 characters. The check runs on the page and takes a fraction of a second at that size. At most 1,000 findings are shown. Invalid YAML is reported with the line and column of the problem, and no rules are run on it.
Privacy
This tool runs entirely in your browser. What you paste is processed on your device and is not sent to a server. The page does not write your input to local storage, cookies or the URL, and the tool does not send your input anywhere. Secret values are masked in the findings and in the copied report.