IF THE PROJECT JUST RUNS IN DOCKER, AUTOMATICALLY DENIED
I HAVE READ .github/CONTRIBUTING.md
Write the sentence: "This project exists to ____."
This project exists to lint Docker Compose files for security misconfigurations. Its object of work is the Compose file itself — take Docker away and it has no reason to exist.
What changed and why:
Adds compose-lint to the Security section (alphabetical, between Checkov and container-explorer).
compose-lint is a static-analysis security linter for docker-compose.yml / compose.yaml. It catches privileged containers, missing cap_drop/no-new-privileges, host namespace sharing, wildcard port binds, unpinned images, Docker socket mounts, sensitive bind mounts, and plaintext credentials — every rule cites the OWASP Docker Security Cheat Sheet or the CIS Docker Benchmark, with specific fix guidance per finding.
Why Security rather than the Linter subsection: the Linter subsection sits under Building Images and is Dockerfile-oriented (Hadolint et al.); compose-lint targets runtime/deployment configuration and fits the same niche as Checkov and KICS, but specialized for Compose. Happy to move it if you prefer otherwise.
Quality signals:
Active: released on PyPI and Docker Hub (distroless, multi-arch, nonroot, Sigstore-signed, SLSA provenance), CI on Python 3.10–3.14.
Ships a State of Docker Compose Security report from scanning 6,444 public Compose files: 91% of those that parse had at least one finding, 68% HIGH or CRITICAL.
Entry passes make lint locally (OK: 0 warnings): one GitHub link, one-sentence verb-first description, Docker connection explicit, alphabetical order preserved.
🔄 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/1466
**Author:** [@tmatens](https://github.com/tmatens)
**Created:** 6/10/2026
**Status:** 🔄 Open
**Base:** `master` ← **Head:** `add-compose-lint`
---
### 📝 Commits (1)
- [`81c69d5`](https://github.com/veggiemonk/awesome-docker/commit/81c69d59d2aafc4b13fbdb821741748a167eb41d) Add compose-lint to Security
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
# IF THE PROJECT JUST RUNS IN DOCKER, AUTOMATICALLY DENIED
- [x] I HAVE READ .github/CONTRIBUTING.md
Write the sentence: *"This project exists to ____."*
**This project exists to lint Docker Compose files for security misconfigurations.** Its object of work is the Compose file itself — take Docker away and it has no reason to exist.
What changed and why:
Adds [compose-lint](https://github.com/tmatens/compose-lint) to the **Security** section (alphabetical, between Checkov and container-explorer).
compose-lint is a static-analysis security linter for `docker-compose.yml` / `compose.yaml`. It catches privileged containers, missing `cap_drop`/`no-new-privileges`, host namespace sharing, wildcard port binds, unpinned images, Docker socket mounts, sensitive bind mounts, and plaintext credentials — every rule cites the OWASP Docker Security Cheat Sheet or the CIS Docker Benchmark, with specific fix guidance per finding.
Why Security rather than the Linter subsection: the Linter subsection sits under *Building Images* and is Dockerfile-oriented (Hadolint et al.); compose-lint targets runtime/deployment configuration and fits the same niche as Checkov and KICS, but specialized for Compose. Happy to move it if you prefer otherwise.
Quality signals:
- Active: released on [PyPI](https://pypi.org/project/compose-lint/) and [Docker Hub](https://hub.docker.com/r/composelint/compose-lint) (distroless, multi-arch, nonroot, Sigstore-signed, SLSA provenance), CI on Python 3.10–3.14.
- [OpenSSF Best Practices passing](https://www.bestpractices.dev/projects/12472) and OpenSSF Scorecard tracked.
- Ships a [*State of Docker Compose Security* report](https://github.com/tmatens/compose-lint/blob/main/docs/state-of-compose.md) from scanning 6,444 public Compose files: 91% of those that parse had at least one finding, 68% HIGH or CRITICAL.
Entry passes `make lint` locally (`OK: 0 warnings`): one GitHub link, one-sentence verb-first description, Docker connection explicit, alphabetical order preserved.
---
<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/1466
Author: @tmatens
Created: 6/10/2026
Status: 🔄 Open
Base:
master← Head:add-compose-lint📝 Commits (1)
81c69d5Add compose-lint to Security📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
IF THE PROJECT JUST RUNS IN DOCKER, AUTOMATICALLY DENIED
Write the sentence: "This project exists to ____."
This project exists to lint Docker Compose files for security misconfigurations. Its object of work is the Compose file itself — take Docker away and it has no reason to exist.
What changed and why:
Adds compose-lint to the Security section (alphabetical, between Checkov and container-explorer).
compose-lint is a static-analysis security linter for
docker-compose.yml/compose.yaml. It catches privileged containers, missingcap_drop/no-new-privileges, host namespace sharing, wildcard port binds, unpinned images, Docker socket mounts, sensitive bind mounts, and plaintext credentials — every rule cites the OWASP Docker Security Cheat Sheet or the CIS Docker Benchmark, with specific fix guidance per finding.Why Security rather than the Linter subsection: the Linter subsection sits under Building Images and is Dockerfile-oriented (Hadolint et al.); compose-lint targets runtime/deployment configuration and fits the same niche as Checkov and KICS, but specialized for Compose. Happy to move it if you prefer otherwise.
Quality signals:
Entry passes
make lintlocally (OK: 0 warnings): one GitHub link, one-sentence verb-first description, Docker connection explicit, alphabetical order preserved.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.