PAGES
← all tools
◆ UNCATEGORIZED

DockSec

v2026.9.21 open-source

DockSec is an OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Lab Project AI-powered Docker security scanner that explains vulnerabilities in plain English.

Summary

DockSec is an open-source static analysis cyber tool that scans Dockerfiles, images, and Compose files for security vulnerabilities and suggests remediation actions. It runs as a CLI tool and is aimed at application developers. Its documentation positions it alongside vulnerability scanners and build linters, and it supports multi-LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. providers for analysis. The project has had 233 commits in the past year and three releases within the tracked period.

DockSec is an OWASP Lab Project AI-powered Docker security scanner that explains vulnerabilities in plain English.

How DockSec helps

Which Dockerfile or image contains security vulnerabilities?

Scans Dockerfiles and images for security vulnerabilities and suggests remediation actions.

How do I scan a multi-service application defined in a compose file?

Scans Docker Compose projects and services for security vulnerabilities.

Can I generate a report from my scan results that displays well in CI/CD logs or pull requests?

Emits a report formatted for native rendering in CI/CD environments.

What are the steps to fix the issues found during a scan?

Provides actionable remediation commands alongside each finding that can be used to fix issues.

Which sources can be used to analyze the container image for vulnerabilities?

Supports analysis using multiple Large Language Model providers.

How can I prioritize the findings I get so I know what to fix first?

Scans and provides a prioritized list of issues, such as those scored by EPSS.

all 18 features, with the evidence for each →

Languages

Not documented

Features

18 capabilities · 3 backed by code, an API document or a real run

Built from DockSec's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What DockSec offers you

  • Command-line interface8
  • CI/CD pipeline integration5
  • Air-gapped deployment1
  • JSON data export1
  • Offline mode1
All capabilities 18 capabilities
Dockerfile static analysis shipped Performs high-speed static analysis directly on Dockerfiles, replacing hardcoded configuration scores with actual structural analysis. 4 releases · 5 other sources · first seen May 2026

Also counts toward: Command-line interface

release

  • Introduces offline mode for scanning environments without network access v2026.7.3 · Jul 2026 · source · release history
  • --severity flag added to control the vulnerability scan scope for images v2026.7.1 · Jul 2026 · source · release history
  • --fail-on gate with CI-friendly exit codes (0/1/2/3) v2026.7.1 · Jul 2026 · source · release history
  • --baseline and --update-baseline flags added for ratchet mode v2026.7.1 · Jul 2026 · source · release history

example

  • Save detailed scan logs to a specific file for later analysis or debugging. docksec --log-file /var/log/docksec/scan.log scan v2026.7.4 · Jul 2026 · source
  • Export dependencies for a container image without requiring internet access. docksec scan --image myapp:latest --sbom --offline v2026.7.3 · Jul 2026 · source
  • Update the baseline with current findings so future scans ratchet against this version. docksec scan --update-baseline v2026.7.1 · Jul 2026 · source
  • Run a scan that only reports vulnerabilities above critical severity and fails the CI step if any are found. docksec scan --severity critical --fail-on 1 v2026.7.1 · Jul 2026 · source
  • Run a static analysis scan against a Dockerfile directly, storing results automatically in the new default directory. docksec --scan-only Dockerfile v2026.5.22 · May 2026 · source
Report generation shipped Outputs structured findings in various formats, including JSON for scripting and customizable directories. 6 releases · 2 other sources · first seen Jul 2026

Also counts toward: JSON data export

release

  • Adds markdown as an output format for reports via --format markdown (in addition to existing formats) v2026.9.21 · Sep 2026 · source · release history
  • Adds markdown report format via --format markdown for CI/CD pipelines v2026.9.20rc1 · Sep 2026 · source · release history
  • Adds --sbom flag to export Software Bill of Materials in SPDX JSON format v2026.7.3 · Jul 2026 · source · release history
  • --sarif flag enables SARIF output format for findings v2026.7.1 · Jul 2026 · source · release history
  • --json flag enables machine-readable JSON output on stdout v2026.7.1 · Jul 2026 · source · release history
  • --format and --output-dir flags to select report format and output directory v2026.7.1 · Jul 2026 · source · release history

example

  • Generate a SARIF report in a specific directory for upload to GitHub Security. docksec scan --format sarif --output-dir ./reports v2026.7.1 · Jul 2026 · source
  • Output JSON findings for scripting docksec -i myapp:latest --image-only --json | jq '.severity_counts'
Risk prioritization verified Applies EPSS-based priority scoring to structured findings to surface exploitability likelihood alongside severity. 6 releases · 2 other sources · first seen Sep 2026

release

  • Introduces EPSS priority calculation as part of the deterministic core scoring engine. v2026.9.20 · Sep 2026 · source · release history
  • Enables EPSS priority ordering for deterministic scanning results v2026.9.20rc3 · Sep 2026 · source · release history
  • Introduces EPSS-based prioritization in deterministic scoring engine v2026.9.20rc1 · Sep 2026 · source · release history
  • EPSS-based scoring prioritizes findings using Exploit Prediction Scoring System data for actionable triage. v2026.9.20rc2 · Sep 2026 · source · release history
  • Introduces EPSS-based priority scoring to rank findings by exploit likelihood v2026.9.21 · Sep 2026 · source · release history
  • Adds EPSS-based priority scoring to structured findings output, surfacing exploitability likelihood alongside severity. v2026.9.21 · Sep 2026 · source · release history

command line

  • --no-epss — Skip the EPSS exploitation-likelihood lookup and rank findings by severity alone (only CVE IDs are ever sent; implied by --offline) v2026.9.20rc1 · Sep 2026 · command-line history

example

  • Prioritize scan results based on real-world exploit probability using EPSS data docksec --epss-priority scan image_name:tag v2026.9.21 · Sep 2026 · source
Attack chain correlation shipped Uses AI-driven analysis to group related issues into coherent attack paths rather than isolated findings. 6 releases · first seen Sep 2026

release

  • Enables AI correlation to identify exploit chains across container services. v2026.9.20 · Sep 2026 · source · release history
  • AI correlation engine detects exploit chains across multiple findings to prioritize risk based on real-world attack paths. v2026.9.20rc2 · Sep 2026 · source · release history
  • Enables AI correlation to identify and group related vulnerabilities into exploit chains v2026.9.21 · Sep 2026 · source · release history
  • Introduces AI correlation for detecting exploit chains across findings v2026.9.20rc3 · Sep 2026 · source · release history
  • AI correlation engine now detects and links exploit chains between findings v2026.9.20rc1 · Sep 2026 · source · release history
  • Adds AI-driven finding correlation and exploit-chain analysis to group related issues into attack paths. v2026.9.21 · Sep 2026 · source · release history
CI integration reports verified Generates markdown reports sized for CI/CD pipeline logs, allowing findings to render natively in job summaries. 2 releases · 4 other sources · first seen Sep 2026

Also counts toward: CI/CD pipeline integration, Command-line interface

release

  • Markdown report format available for CI/CD pipelines with --format markdown. v2026.9.20rc2 · Sep 2026 · source · release history
  • Adds markdown report format support via --format flag for CI/CD integration v2026.9.20rc3 · Sep 2026 · source · release history

command line

  • --no-install-recommends — to `apt-get install`, and converts `ADD` to `COPY` v2026.9.20rc1 · Sep 2026 · command-line history

example

  • Generate a markdown report for CI/CD pipelines to enable better integration with PR workflows. docksec scan --format markdown . > report.md v2026.9.20rc2 · Sep 2026 · source
  • Emit a markdown report in CI so GitHub Actions or GitLab MR pipelines render findings natively in the job summary. docksec scan myapp:latest --format markdown > docksec-report.md v2026.9.20rc1 · Sep 2026 · source
  • Generate a Markdown report suitable for pasting into GitHub Actions or GitLab CI logs. docksec scan --image myapp:latest --format markdown > findings.md v2026.9.20rc1 · Sep 2026 · source
Artifact distribution shipped Publishes the container image to GitHub Container Registry (GHCR) as a new distribution channel. 5 releases · first seen Sep 2026

release

  • Adds support for publishing container images to GitHub Container Registry (GHCR) v2026.9.21 · Sep 2026 · source · release history
  • Publishes the container image to GHCR, providing a new distribution channel alongside the existing packaging. v2026.9.21 · Sep 2026 · source · release history
  • Container images now published to GitHub Container Registry (GHCR) at ghcr.io/owasp/docksec. v2026.9.20rc2 · Sep 2026 · source · release history
  • Publishes container images to GitHub Container Registry (GHCR) for installation. v2026.9.20 · Sep 2026 · source · release history
  • Publishes container image to GitHub Container Registry (GHCR) via consolidated packaging v2026.9.20rc3 · Sep 2026 · source · release history
Scan failure gating shipped Controls CI/CD pipeline outcomes by failing scans based on specific severity thresholds or vulnerability counts. 2 releases · 1 other source · first seen Jul 2026

Also counts toward: CI/CD pipeline integration, Command-line interface

release

  • --severity flag added to control the vulnerability scan scope for images v2026.7.1 · Jul 2026 · source · release history
  • --fail-on gate with CI-friendly exit codes (0/1/2/3) v2026.7.1 · Jul 2026 · source · release history

example

  • Run a scan that only reports vulnerabilities above critical severity and fails the CI step if any are found. docksec scan --severity critical --fail-on 1 v2026.7.1 · Jul 2026 · source
Docker Compose scanning shipped Supports security scanning for Docker Compose projects and multi-service orchestration configurations. 1 release · 1 other source · first seen Jun 2026

release

  • Adds docker compose security scanning and multi-service orchestration support v2026.6.11 · Jun 2026 · source · release history

example

  • Scan a docker-compose project and automatically apply safe fixes for critical vulnerabilities docksec --format markdown --fix scan compose.yml v2026.9.21 · Sep 2026 · source
Remediation assistance shipped Provides prioritized fix lists ordered by EPSS score and generates actionable remediation commands inline with findings. 1 release · 1 other source · first seen Sep 2026

Also counts toward: Command-line interface

release

  • Adds the --fix flag to enable remediation commands directly from findings. v2026.9.20 · Sep 2026 · source · release history

example

  • Scan an image and immediately get a prioritized fix list ordered by EPSS score, with remediation commands printed inline. docksec scan myapp:latest --fix v2026.9.20rc1 · Sep 2026 · source
Supply chain integrity shipped Provides signed releases and self-scanning CI capabilities to verify the integrity of DockSec artifacts. 2 releases · first seen Sep 2026

Also counts toward: CI/CD pipeline integration, Command-line interface

release

  • Adds --fix subcommand to self-scanning CI workflows v2026.9.20rc3 · Sep 2026 · source · release history
  • Adds signed releases and self-scanning CI with integration guides. v2026.9.20 · Sep 2026 · source · release history
Detailed CLI logging shipped Captures detailed scan logs to a specified file for debugging and post-scan analysis. 1 release · 1 other source · first seen Jul 2026

release

  • Adds .docksec.yml as the new repo-level configuration file for DockSec v2026.8.19 · Aug 2026 · source · release history

example

  • Save detailed scan logs to a specific file for later analysis or debugging. docksec --log-file /var/log/docksec/scan.log scan v2026.7.4 · Jul 2026 · source
Offline scanning capability shipped Enables vulnerability analysis in network-isolated environments without requiring external connectivity. 1 release · 1 other source · first seen Jul 2026

Also counts toward: Air-gapped deployment, Offline mode

release

  • Introduces offline mode for scanning environments without network access v2026.7.3 · Jul 2026 · source · release history

example

  • Export dependencies for a container image without requiring internet access. docksec scan --image myapp:latest --sbom --offline v2026.7.3 · Jul 2026 · source
Baseline drift detection shipped Tracks vulnerabilities relative to a previous scan baseline to identify new regressions or improvements over time. 1 release · 1 other source · first seen Jul 2026

Also counts toward: Command-line interface

release

  • --baseline and --update-baseline flags added for ratchet mode v2026.7.1 · Jul 2026 · source · release history

example

  • Update the baseline with current findings so future scans ratchet against this version. docksec scan --update-baseline v2026.7.1 · Jul 2026 · source
CI scan completeness control verified Defines how the tool handles incomplete scans in CI pipelines, allowing options to warn and continue or fail the build. 1 other source · first seen Sep 2026

Also counts toward: CI/CD pipeline integration, Command-line interface

command line

  • --incomplete-policy — What to do when a scanner could not run: 'warn' reports the gap and continues (default), 'fail' exits 3 so CI cannot pass on an incomplete scan v2026.9.20rc1 · Sep 2026 · command-line history
Repository configuration management shipped Manages tool settings and configurations via a dedicated repository-level configuration file. 1 release · first seen Aug 2026

release

  • Adds .docksec.yml as the new repo-level configuration file for DockSec v2026.8.19 · Aug 2026 · source · release history
GitHub Actions integration shipped Integrates with GitHub Actions to post scan results directly as pull request comments and scan Compose files within the action. 1 release · first seen Jun 2026

Also counts toward: CI/CD pipeline integration

release

  • Adds docker compose file scanning capability within the GitHub Action v2026.6.12 · Jun 2026 · source · release history
Cost-aware model selection shipped Automatically selects the most cost-effective available model, such as claude-haiku-4-5, instead of defaulting to more expensive options. 1 release · first seen May 2026

Also counts toward: Command-line interface

release

  • --smart-model-selection enables automatic selection of cost-effective models like claude-haiku-4-5 across providers. v2026.5.22.1 · May 2026 · source · release history
Multi-LLM provider support shipped Supports multiple large language model providers such as OpenAI, Anthropic, Google, and Ollama for vulnerability analysis. 1 release · first seen Feb 2026

release

  • Add multi-LLM provider support (OpenAI, Anthropic, Google, Ollama) v2026.2.23 · Feb 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for DockSec, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail DockSec puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

15 entries

  1. September 20265
  2. August 20261
  3. July 20263
  4. June 20262
  5. May 20262
  6. April 20261
  7. February 20261
    Show

    15 entries

    Project health

    Issue, contributor and maintainer activity in OWASP/DockSec, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 19 +14 vs prior 12 months
    2. Maintainers 1 +0 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 37% of issues opened, last 12 months
    5. Median time to close 52 days first maintainer reply 38 days
    6. Open backlog 5 of 27 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 5
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars not measured
    Issue themes, last 12 months
    • bugs 11%
    • features 52%
    • docs 4%
    • other 33%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →