This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
dockersec
Scan Dockerfiles for security issues. Offline. Free.
dockersec is an offline CLI security scanner for Dockerfiles and docker-compose files. 28 built-in rules, GitHub Actions ready, ships as a single Go binary.
I built dockersec because I kept seeing the same Docker security mistakes show up in production codebases , containers running as root, API keys hardcoded in ENV, base images that change silentlyevery week.
The existing tools either required a cloud account, called home on every scan, or only checked a handful of issues. I wanted something that runs offline, ships as a single binary, and gives you actionable fix instructions instead of just a list of CVE IDs.
So I built it in Go over a few weeks. It now covers 28 rules across Dockerfile and docker-compose files, has a YAML rule engine so anyone can add rules without writing Go, and ships binaries for Linux, macOS, and Windows via goreleaser.
The thing I'm most proud of: the fix instructions. Each finding tells you not just what's wrong but exactly why it matters and what to type to fix it. I wrote them for someone who is new to Docker security, not just for experts.
Would love to hear what rules you think are missing.
“Scan Dockerfiles for security issues. Offline. Free.”
dockersec was submitted on Product Hunt and earned 5 upvotes and 1 comments, placing #29 on the daily leaderboard. dockersec is an offline CLI security scanner for Dockerfiles and docker-compose files. 28 built-in rules, GitHub Actions ready, ships as a single Go binary.
On the analytics side, dockersec competes within Open Source, Developer Tools, GitHub and Security — topics that collectively have 626.4k followers on Product Hunt. The dashboard above tracks how dockersec performed against the three products that launched closest to it on the same day.
Who hunted dockersec?
dockersec was hunted by DEEPAK M S. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of dockersec including community comment highlights and product details, visit the product overview.
Hey Product Hunt! 👋
I built dockersec because I kept seeing the same Docker security mistakes show up in production codebases , containers running as root, API keys hardcoded in ENV, base images that change silentlyevery week.
The existing tools either required a cloud account, called home on every scan, or only checked a handful of issues. I wanted something that runs offline, ships as a single binary, and gives you actionable fix instructions instead of just a list of CVE IDs.
So I built it in Go over a few weeks. It now covers 28 rules across Dockerfile and docker-compose files, has a YAML rule engine so anyone can add rules without writing Go, and ships binaries for Linux, macOS, and Windows via goreleaser.
The thing I'm most proud of: the fix instructions. Each finding tells you not just what's wrong but exactly why it matters and what to type to fix it. I wrote them for someone who is new to Docker security, not just for experts.
Would love to hear what rules you think are missing.
Website: https://deepakms.com/projects/dockersec.html
GitHub: https://github.com/Deepak-coder80/dockersec