What it does: Free, client-side Dockerfile security linter with 18 rules across 4 categories (Security, Best Practices, Performance, Maintainability). Everything runs in the browser — the Dockerfile never leaves the user's device.
Why it belongs here:
Docker-specific tool (lints Dockerfiles)
Active GitHub repository with MIT license
18 rules covering real security issues (running as root, hardcoded secrets, using latest tag, etc.)
Client-side only — no server dependency
Resubmitting after fixing the contributing guideline issue from the previous PR (was linking to a marketing page — now linking to the GitHub repository directly).
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/veggiemonk/awesome-docker/pull/1271
**Author:** [@Matheus-RR](https://github.com/Matheus-RR)
**Created:** 3/12/2026
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `add-dockerfile-linter-v2`
---
### 📝 Commits (2)
- [`c23483b`](https://github.com/veggiemonk/awesome-docker/commit/c23483b3b6f12da63fba0c3ba742c42db1851f42) Add Dockerfile Linter to Linter section
- [`5346258`](https://github.com/veggiemonk/awesome-docker/commit/53462588286843d0862ccb3db1b47fb3c384cee6) Add releaserun-dockerfile-linter to Linting section
### 📊 Changes
**1 file changed** (+2 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+2 -0)
</details>
### 📄 Description
## Summary
Adding [releaserun-dockerfile-linter](https://github.com/Releaserun/releaserun-dockerfile-linter) to the Linter section.
**What it does:** Free, client-side Dockerfile security linter with 18 rules across 4 categories (Security, Best Practices, Performance, Maintainability). Everything runs in the browser — the Dockerfile never leaves the user's device.
**Why it belongs here:**
- Docker-specific tool (lints Dockerfiles)
- Active GitHub repository with MIT license
- 18 rules covering real security issues (running as root, hardcoded secrets, using `latest` tag, etc.)
- Client-side only — no server dependency
Resubmitting after fixing the contributing guideline issue from the previous PR (was linking to a marketing page — now linking to the GitHub repository directly).
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/1271
Author: @Matheus-RR
Created: 3/12/2026
Status: ❌ Closed
Base:
master← Head:add-dockerfile-linter-v2📝 Commits (2)
c23483bAdd Dockerfile Linter to Linter section5346258Add releaserun-dockerfile-linter to Linting section📊 Changes
1 file changed (+2 additions, -0 deletions)
View changed files
📝
README.md(+2 -0)📄 Description
Summary
Adding releaserun-dockerfile-linter to the Linter section.
What it does: Free, client-side Dockerfile security linter with 18 rules across 4 categories (Security, Best Practices, Performance, Maintainability). Everything runs in the browser — the Dockerfile never leaves the user's device.
Why it belongs here:
latesttag, etc.)Resubmitting after fixing the contributing guideline issue from the previous PR (was linking to a marketing page — now linking to the GitHub repository directly).
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.