PAGES
← all tools
◆ Container & Image Security

Trivy

changelog-20261005-4ed51b71 open-source

Trivy is a comprehensive security scanner that finds vulnerabilities, misconfigurations, secrets, and SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. in containers, Kubernetes, code repositories, and clouds

Summary

Trivy is an open-source, free command-line scanner that checks container images, filesystems, git repositories, virtual machine images, and Kubernetes clusters for known vulnerabilities, misconfigurations, exposed secrets, and outdated licenses, and can also generate SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. in formats like CycloneDXCycloneDXAn open standard for describing software components and their dependencies, vulnerabilities and other supply-chain information. Tools use it to exchange bills of materials and related evidence. and SPDXSPDXAn open standard for describing software components, licenses and their relationships. Its documents let different tools exchange a software bill of materials without inventing a new format.. It is aimed at application developers and platform teams who need to catch issues before or after deployment, and it fits into pipelines through GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure., a Kubernetes operator, or a VS Code plugin rather than running as a standalone service. First committed in 2019, it has drawn 562 contributors and shipped a release this week, putting it in active, ongoing development.

Trivy is a comprehensive security scanner that finds vulnerabilities, misconfigurations, secrets, and SBOM in containers, Kubernetes, code repositories, and clouds

How Trivy helps

Which known vulnerabilities are lurking in the images and dependencies I ship?

scans OS packages and language dependencies inside the image or filesystem against CVE databases, including OS-specific ones like Bottlerocket's advisory feed, and lists each affected package with its fixed version

Which of my Terraform, Kubernetes, or CloudFormation files would fail a security review before they ever get applied?

runs built-in misconfiguration checks against the IaC source and reports each violated rule with the file and resource, before anything is deployed

Have I committed API keys, tokens, or passwords anywhere in this codebase or image?

walks the filesystem or repository content against pattern-matching rules for services like GitHub, Azure, and OpenAI and reports each match with the file and line

What open-source components and licenses am I actually shipping in this build?

builds a software bill of materials from detected OS packages and language dependencies, extracting license data even from files embedded inside JARs, in CycloneDX or SPDX format

Does my self-contained .NET app carry vulnerabilities in the runtime it bundles?

inspects self-contained deployments for the embedded runtime version and checks it against known CVEs, not just the application's own dependencies

Is my live Kubernetes cluster running workloads with unpatched or misconfigured images right now?

connects to the cluster and scans the workloads deployed in it, returning a summary report of vulnerabilities and misconfigurations found across resources

all 38 features, with the evidence for each →

Languages

Not documented

Features

38 capabilities across 6 capability groups · 3 backed by code, an API document or a real run

Built from Trivy'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 →

  • Trivy covers 4 of the 8 vulnerability assessment methods capabilities we track.
  • Trivy covers 2 of the 5 supply chain security capabilities we track.

What Trivy offers you

  • Command-line interface7
  • JSON data export2
  • CI/CD pipeline integration1
  • Plugin system1
  • Scripting language support1
  • MCP server
Static application security testing 4 features Vulnerability assessment methods since 2019
Filesystem and local project scanning verified Scans a local project directory or filesystem for vulnerabilities, secrets, and misconfigurations in one pass. 25 releases · 8 other sources · first seen Jun 2020

Shared capability: Static application security testing

release 25 total

  • Supports uv workspace lockfiles. changelog · Oct 2026 · source · release history
  • Configuration files can be disabled by passing empty paths via CLI 0.75.0 · Oct 2026 · source · release history
  • Dereference all Maven settings.xml environment placeholders 0.64.0 · Jun 2025 · source · release history
  • nodejs: recognizes root and workspace dependencies for yarn lockfiles 0.62.0 · Apr 2025 · source · release history
  • Uses toolchain as stdlib version for go.mod files 0.55.0 · Sep 2024 · source · release history
  • Add sbt project support via sbt-dependency-lock for dependency lock file parsing in Scala projects 0.53.0 · Jul 2024 · source · release history

docs

  • Scans container images, filesystems, Git repos, VMs, and Kubernetes clusters for CVEs, misconfigurations, secrets, and license issues.

example

  • Run a scan without loading any configuration files by specifying empty paths. trivy image --config "" --policy "" <image_name> 0.75.0 · Oct 2026 · source
  • Perform a fully offline scan on a local directory for air-gapped environments. trivy fs --offline-scan ./my-project v0.22.0 · Dec 2021 · source
  • Skip database updates during filesystem scanning for faster execution in offline or cached environments. trivy fs --skip-update /path/to/project v0.12.0 · Oct 2020 · source
  • Scan a local project directory for known vulnerabilities using lock files. trivy fs /path/to/my/project v0.9.0 · Jun 2020 · source
  • Scan a local project for vulns, secrets, misconfigs trivy fs --scanners vuln,secret,misconfig .
  • Scan filesystem for vulns, secrets, misconfigs trivy fs --scanners vuln,secret,misconfig myproject/

mcp

  • scan_filesystem
Secret scanning shipped Detects secrets and credentials committed to codebases, with configurable rules and exclusions covering a broad range of token types. 15 releases · 4 other sources · first seen May 2019

Shared capability: Static application security testing

release 15 total

  • Allows disabling configuration files with empty paths. changelog · Oct 2026 · source · release history
  • Adds detection of the new stateless format for GitHub App installation tokens in secrets scanning. v0.72.0 · Jun 2026 · source · release history
  • Adds OpenAI secret detection rules to the secrets scanner. v0.72.0 · Jun 2026 · source · release history
  • New detection rules for OpenAI secrets 0.72.0 · Jun 2026 · source · release history
  • Enables customization of folders, files, and extensions skipped during secret scanning. v0.71.0 · Jun 2026 · source · release history
  • Adds Azure-specific secret detection rules to the secret scanner engine 0.71.0 · Jun 2026 · source · release history

example

  • Scan a codebase for leaked OpenAI API keys and the new stateless GitHub App installation token format alongside other secrets. trivy fs --scanners secret <your-repo-path/> v0.72.0 · Jun 2026 · source
  • Scan a project for secrets while skipping a custom secrets config file, vendor directories, and specific extensions you know are safe. trivy fs --scanners secret myproject/ v0.71.0 · Jun 2026 · source
  • Scan a private Helm repository requiring authentication. trivy image --format json --helm.server-token "${HELM_SERVER_TOKEN}" oci://private-registry.io/chart-repo/mychart:1.0.0 v0.24.3 · Mar 2022 · source
  • Clear the global Trivy cache without targeting a specific image. trivy --clear-cache v0.0.14 · May 2019 · source
Remote repository scanning verified Scans a remote git repository for vulnerabilities, secrets, and misconfigurations without requiring a local clone. 2 releases · 3 other sources · first seen May 2019

Shared capability: Static application security testing

release

  • Adds the repo subcommand to scan remote public Git repositories (e.g., https://github.com/aquasecurity/trivy-ci-test") v0.9.0 · Jun 2020 · source · release history
  • --depth argument passed to git clone allows shallow clones for faster repository scanning. v0.1.2 · May 2019 · source · release history

example

  • Check a public GitHub repository for dependencies with known vulnerabilities. trivy repo https://github.com/example-org/public-repo v0.9.0 · Jun 2020 · source
  • Scan a remote git repository trivy repo https://github.com/owner/repo

mcp

  • scan_repository
Enhanced Go module dependency resolution shipped Constructs Go module dependencies directly in the parser to improve detection accuracy for application libraries. 2 releases · first seen Dec 2024

Shared capability: Static application security testing

release

  • Support for new stateless format for GitHub App installation tokens 0.72.0 · Jun 2026 · source · release history
  • Construct Go module dependencies directly in the parser for better accuracy 0.58.0 · Dec 2024 · source · release history
Vulnerability database matching 3 features Vulnerability assessment methods since 2019
OS target detection shipped Identifies the operating system of a scan target so that vulnerability data is matched against the correct OS-level advisory database. 13 releases · first seen Aug 2019

Shared capability: Vulnerability database matching

release 13 total

  • New vulnerability matching for Bottlerocket OS targets 0.72.0 · Jun 2026 · source · release history
  • Adds vendor directory support for language file detection in SEAL scanning. v0.71.0 · Jun 2026 · source · release history
  • Adds detection capability for Ubuntu 26.04 LTS operating system 0.71.0 · Jun 2026 · source · release history
  • Detects Ubuntu 26.04 LTS as a recognized OS target. v0.71.0 · Jun 2026 · source · release history
  • Adds SUSE Linux Enterprise Micro as a supported platform for vulnerability detection 0.56.0 · Oct 2024 · source · release history
  • openSUSE tumbleweed detection and scanning 0.54.0 · Jul 2024 · source · release history
Vulnerability database management shipped Allows users to manage the vulnerability database independently of scanning, including downloading the database only or updating it without performing a scan. 5 releases · 2 other sources · first seen May 2019

Shared capability: Vulnerability database matching

Also counts toward: Command-line interface

release

  • Adds support for multiple vulnerability and Java database repositories via --db-repo 0.56.0 · Oct 2024 · source · release history
  • Supports PAR files in Java language-specific package scanning. v0.23.0 · Jan 2022 · source · release history
  • The Trivy DB is now fetched from GHCR (ghcr.io) by default instead of the previous source. v0.23.0 · Jan 2022 · source · release history
  • Re-implements the --cache-dir flag to allow specifying a custom cache directory path v0.1.5 · Aug 2019 · source · release history
  • --only-update flag added to update only the existing vulnerability database without running a scan. v0.1.2 · May 2019 · source · release history

example

  • Pull the latest vulnerability definitions from a private OCI registry instead of the default public one. trivy image --db-repository my-registry.internal/trivy-db alpine:latest v0.25.1 · Apr 2022 · source
  • Store the vulnerability database in a specific local directory for faster subsequent scans. trivy image --cache-dir /tmp/trivy-cache alpine:latest v0.1.5 · Aug 2019 · source
RPM archive scanning shipped Scans RPM archives for vulnerabilities by recognizing the package format and matching it against the vulnerability database. 1 release · first seen Oct 2024

Shared capability: Vulnerability database matching

release

Container image vulnerability scanning 2 features Vulnerability assessment methods since 2019
Container image scanning shipped Scans container images for known vulnerabilities, including images built on specialised operating systems. 43 releases · 18 other sources · first seen May 2019

Shared capability: Container image vulnerability scanning

release 43 total

  • Adds vulnerability detection for Echo-patched Python packages. changelog · Oct 2026 · source · release history
  • Classifies julia, bottlerocket, and centos stream packages. changelog · Oct 2026 · source · release history
  • Adds vulnerability matching for Bottlerocket OS images. v0.72.0 · Jun 2026 · source · release history
  • Adds WithDriver and WithProvider options to the ospkg detector for custom operating system package sources 0.71.0 · Jun 2026 · source · release history
  • Adds support for ActiveState images 0.69.0 · Jan 2026 · source · release history
  • Adds os-release detection for RHEL-based images in the vulnerability scanner to improve package identification accuracy 0.67.0 · Sep 2025 · source · release history

example 18 total

  • Scan a Bottlerocket-based container image for OS-level CVEs — now matched against the Bottlerocket advisory database. trivy image --scanners vuln <bottlerocket-based-image> v0.72.0 · Jun 2026 · source
  • Scan a container image while forcing the vulnerability database to treat it as Debian Bookworm, regardless of the base image metadata. trivy image --distro debian:bookworm myimage:latest 0.59.0 · Jan 2025 · source
  • Scan a container image or filesystem while tuning false positive rates by setting detection priority. trivy --detection-priority high target-image 0.55.0 · Sep 2024 · source
  • Scan a container image and output SARIF results with local ImageID for tracking in vulnerability management tools. trivy image --format sarif --output result.sarif myimage:latest 0.53.0 · Jul 2024 · source
  • Disable TLS verification when scanning against a local registry with a self-signed cert trivy image --tls-insecure-skip-verify localhost:5000/myimage:v1 v0.24.0 · Feb 2022 · source
  • Scan an image built with Podman locally. trivy image localhost/test:latest v0.16.0 · Feb 2021 · source
Container build tool integration shipped Extends scanning capabilities to support outputs from specific container build tools like Kaniko. 2 releases · first seen Oct 2019

Shared capability: Container image vulnerability scanning

release

  • Adds feat(cache): introduce versioned cache to manage cache versions explicitly v0.17.0 · Apr 2021 · source · release history
  • Support for Kaniko build tool outputs v0.1.7 · Oct 2019 · source · release history
Infrastructure-as-code security scanning 1 feature Vulnerability assessment methods since 2026
Ansible playbook scanning verified Scans Ansible playbook files for vulnerabilities and misconfigurations by accepting playbook paths directly at the command line. 1 other source · first seen Jan 2026

Shared capability: Infrastructure-as-code security scanning

command line

  • --ansible-playbook — specify playbook file path(s) to scan v0.69.0 · Jan 2026 · command-line history
SBOM generation 1 feature Supply chain security since 2022
SBOM generation shipped Generates a Software Bill of Materials for a scanned target in standard formats suitable for supply chain and compliance use. 16 releases · 1 other source · first seen Feb 2022

Shared capability: SBOM generation

release 16 total

  • Adds SHA-512 hash algorithm support to the SPDX serializer. v0.71.0 · Jun 2026 · source · release history
  • Enables CycloneDX 1.7 format output in SBOM generation 0.71.0 · Jun 2026 · source · release history
  • Supports Maven <mirrors> configuration from settings.xml when scanning pom.xml dependencies. v0.71.0 · Jun 2026 · source · release history
  • Supports CycloneDX 1.7 SBOM format for both input and output. v0.71.0 · Jun 2026 · source · release history
  • Adds SHA-512 hash algorithm support to the SPDX serializer output format 0.71.0 · Jun 2026 · source · release history
  • Preserves CycloneDX SBOM structure during vulnerability updates when scanning existing SBOM files 0.67.0 · Sep 2025 · source · release history

example

  • Generate a CycloneDX 1.7 SBOM from a container image to take advantage of the latest spec features. trivy image --format cyclonedx --output sbom.cdx.json python:3.12-slim v0.71.0 · Jun 2026 · source
CycloneDX SBOM 1 feature Supply chain security since 2025
Cryptographic asset scanning shipped Scans images and other targets to discover cryptographic assets—including ML-DSA keys and signature algorithms—and reports them in CycloneDX format, with support for client/server mode transfer. 9 releases · 3 other sources · first seen Sep 2025

Shared capability: CycloneDX SBOM

release 9 total

  • Outputs cryptographic assets in CycloneDX format and transfers them in client/server mode. changelog · Oct 2026 · source · release history
  • Supports ML-DSA keys and signature algorithms in cryptographic asset descriptions. changelog · Oct 2026 · source · release history
  • Adds a cryptographic asset model, parser, and analyzer that scans images and passes discovered assets to the scan report via the image command.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ changelog · Oct 2026 · source · release history
  • Output of cryptographic assets is now supported in CycloneDX format 0.75.0 · Oct 2026 · source · release history
  • Cryptographic assets can be described as ML-DSA keys and signature algorithms 0.75.0 · Oct 2026 · source · release history
  • Cryptographic assets can be transferred in client/server mode 0.75.0 · Oct 2026 · source · release history

docs

  • 1040 lines (817 loc) · 157 KB 1040 lines (817 loc) · 157 KB (2026-10-01) remove getHostByName from templates ( #11206 add cryptographic asset model and parser ( #10970 64e1715 allow disabling configuration files with empty paths ( #11210 5f00edd crypto: add analyzer and pass assets to the scan report ( #11104 fb7ad28… changelog · Oct 2026 · source

example

  • Scan a container image and surface its cryptographic assets (keys, certs, signature algorithms) alongside vulnerabilities. trivy image --scanners vuln,crypto <image> changelog · Oct 2026 · source
  • Scan an image for cryptographic assets like ML-DSA keys and export the findings. trivy image --format cyclonedx --scan-crypto <image_name> 0.75.0 · Oct 2026 · source
Other / not yet classified 26 features Features we have not matched to a capability yet. A suggested match is marked.
Misconfiguration scanning shipped Detects infrastructure misconfigurations across cloud and platform configuration files using built-in policy rules. 40 releases · 5 other sources · first seen Dec 2019

Also counts toward: Command-line interface

release 40 total

  • Extends AVD-AWS-0010 misconfiguration check to cover CloudFront standard logging v2. v0.72.0 · Jun 2026 · source · release history
  • Support for CloudFront standard logging v2 in misconf check AVD-AWS-0010 0.72.0 · Jun 2026 · source · release history
  • Adapt misconf rules for ARM-based Kubernetes clusters 0.70.0 · Apr 2026 · source · release history
  • Support azurerm_network_interface_security_group_association in misconf scanning 0.70.0 · Apr 2026 · source · release history
  • Adds initial ansible scanning support for infrastructure-as-code misconfigurations 0.69.0 · Jan 2026 · source · release history
  • misconf: added audit config attribute 0.66.0 · Sep 2025 · source · release history

example

  • Ignore specific misconfiguration warnings in a Helm chart by adding inline comments. # Run trivy config on a Helm chart # Inside values.yaml or templates, add: # trivy:ignore=CVS-2024-XXXX 0.59.0 · Jan 2025 · source
  • Ignore specific misconfiguration warnings in a Dockerfile by adding inline comments. # Run trivy config on a Dockerfile # Inside the Dockerfile, add: RUN apt-get update # trivy:ignore=CVS-2024-XXXX 0.59.0 · Jan 2025 · source
  • Scan a local YAML or JSON configuration file for misconfigurations. trivy config path/to/config.yaml 0.55.0 · Sep 2024 · source
  • Scan a local directory for IaC issues using the new config scanning capability trivy config ./infrastructure/terraform v0.19.0 · Jul 2021 · source
  • Enable verbose trace logging for debugging misconfiguration scans trivy config --trace ./path/to/configs v0.19.0 · Jul 2021 · source
Scan output customization shipped Enables customizing scan results through ignore files and template-based export formats. 18 releases · 1 other source · first seen Oct 2019

release 18 total

  • Add ReportID field to scan reports (switched from UUIDv4 to UUIDv7) 0.68.0 · Dec 2025 · source · release history
  • Add ArtifactID field to uniquely identify scan targets in reports 0.68.0 · Dec 2025 · source · release history
  • Include misconfiguration location information in JUnit output templates 0.63.0 · May 2025 · source · release history
  • Exports modified findings in JSON reports 0.55.0 · Sep 2024 · source · release history
  • Allows misconfigurations to be included in GitLab Codequality report formats via template support v0.25.0 · Mar 2022 · source · release history
  • Logs ignored vulnerabilities when debug logging is enabled. v0.23.0 · Jan 2022 · source · release history

example

  • Export all installed packages in SARIF format for integration with code scanning platforms. trivy image -f sarif --list-all-pkgs centos:7 v0.10.0 · Jul 2020 · source
Java license extraction shipped Extracts license information from Java archive files by reading embedded metadata and bundled licence files. 13 releases · 1 other source · first seen Apr 2022

release 13 total

  • Reports unparsable license names with UNKNOWN severity. changelog · Oct 2026 · source · release history
  • Extracts JAR licenses from packaged LICENSE files inside JARs. v0.72.0 · Jun 2026 · source · release history
  • Detection of JAR licenses from embedded pom.xml files 0.72.0 · Jun 2026 · source · release history
  • Extracts JAR licenses from embedded pom.xml files for more complete Java license inventory. v0.72.0 · Jun 2026 · source · release history
  • Detection of JAR licenses from packaged LICENSE files 0.72.0 · Jun 2026 · source · release history
  • license scanner observes pkg_type option to filter by package type 0.65.0 · Jul 2025 · source · release history

example

  • Scan a JAR file using a custom or corporate Maven mirror instead of the default central repo. TRIVY_MAVEN_URL=https://internal-mirror.example.com/repository/maven-public trivy fs --image my-app.jar v0.25.3 · Apr 2022 · source
Server-client architecture support shipped Provides a client-server model for scanning, allowing separate server and client subcommands to handle database storage and query operations. 8 releases · 3 other sources · first seen Dec 2019

Also counts toward: Command-line interface

release 8 total

  • Include server version info in JSON output for client/server mode 0.70.0 · Apr 2026 · source · release history
  • Adds internal --path-prefix flag for Trivy Server client/server mode 0.55.0 · Sep 2024 · source · release history
  • Adds --cache-backend flag to configure Redis as the image/dictionary cache backend v0.15.0 · Dec 2020 · source · release history
  • Releases Helm chart at helm/trivy for installing Trivy server mode v0.15.0 · Dec 2020 · source · release history
  • Health check endpoint added to Trivy server at /healthz v0.12.0 · Oct 2020 · source · release history
  • --token flag for passing authentication tokens to server/client v0.4.0 · Dec 2019 · source · release history

example

  • Configure Trivy server to use a running Redis instance for faster cache lookups. trivy server --cache-backend redis://localhost:6379 v0.15.0 · Dec 2020 · source
  • Check the health status of a running Trivy server instance. curl http://127.0.0.1:4954/healthz v0.12.0 · Oct 2020 · source
  • Use a custom header name for token authentication when connecting to a Trivy server that expects a non-standard header. trivy server --token my-secret --token-header x-custom-token v0.4.0 · Dec 2019 · source
CI/CD integration support shipped Supports continuous integration workflows through fast scanning modes, environment variable configuration, and GitHub API token handling to bypass rate limits. 6 releases · 4 other sources · first seen Nov 2019

Also counts toward: CI/CD pipeline integration

release

  • Adds --tls-insecure-skip-verify flag to the client/server connection to disable TLS certificate validation v0.24.0 · Feb 2022 · source · release history
  • Enables Redis TLS for the cache backend by setting TRIVY_CACHE_REDIS_TLS_* environment variables. v0.23.0 · Jan 2022 · source · release history
  • AWS Security Hub integration via the security-hub output format for Trivy results v0.11.0 · Aug 2020 · source · release history
  • Adds an initial GitLab CI template for deep integration with GitLab Container Scanning v0.4.4 · Feb 2020 · source · release history
  • GITHUB_TOKEN environment variable is now respected to bypass GitHub API rate limits v0.2.1 · Nov 2019 · source · release history
  • Environment variables can now specify Trivy options (e.g. TRIVY_EXIT_CODE) alongside CLI flags v0.2.0 · Nov 2019 · source · release history

example

  • Enable TLS for the Trivy cache to connect to a secured Redis instance. export TRIVY_CACHE_REDIS_TLS_CERT=/path/to/cert.pem export TRIVY_CACHE_REDIS_TLS_KEY=/path/to/key.pem export TRIVY_CACHE_REDIS_TLS_CA=/path/to/ca.pem trivy image --cache-dir /tmp/trivy-cache… v0.23.0 · Jan 2022 · source
  • Render vulnerability reports as HTML emails for automated notification pipelines. trivy --format template --template "@/path/to/template" golang:1.12-alpine v0.4.3 · Jan 2020 · source
  • Configure Trivy via environment variables to integrate with shell pipelines or CI configs. TRIVY_EXIT_CODE=1 trivy alpine:3.10 v0.2.0 · Nov 2019 · source
  • Run a fast CI/CD scan where download speed matters more than detail granularity. trivy --light alpine:3.10 v0.2.0 · Nov 2019 · source
Plugin management shipped Manages external plugins by listing, viewing details, and updating installed extensions at runtime. 6 releases · 2 other sources · first seen Apr 2021

Also counts toward: Plugin system

release

  • Adds support for a plugin index to discover and install plugins 0.52.0 · Jun 2024 · source · release history
  • Adds ability to specify a concrete version when installing or referencing plugins 0.52.0 · Jun 2024 · source · release history
  • Adds the ability to update installed plugins via a new option v0.21.3 · Dec 2021 · source · release history
  • Adds plugin list and plugin info subcommands to manage installed plugins v0.21.3 · Dec 2021 · source · release history
  • Adds new aqua plugin for extensible detection logic v0.19.0 · Jul 2021 · source · release history
  • Adds feat: support plugins to allow loading external Trivy plugins at runtime v0.17.0 · Apr 2021 · source · release history

example

  • List all currently installed Trivy plugins. trivy plugin list v0.21.3 · Dec 2021 · source
  • View detailed metadata for a specific installed plugin. trivy plugin info <plugin-name> v0.21.3 · Dec 2021 · source
Integration output formats shipped Supports exporting scan results in specialized formats for automated notification pipelines and third-party security platforms like AWS Security Hub. 6 releases · 2 other sources · first seen Jan 2020

Also counts toward: JSON data export

release

  • Enables --format cyclonedx exports to include vulnerability details within the CycloneDX JSON output v0.25.0 · Mar 2022 · source · release history
  • Adds --format cyclonedx to export findings in CycloneDX format v0.24.0 · Feb 2022 · source · release history
  • Adds misconfigurations to JUnit XML report output (--format junit) with new <testcase> elements for each finding v0.24.0 · Feb 2022 · source · release history
  • Enhances the custom-forward integration to include extended advisory data in forwarded outputs v0.20.1 · Oct 2021 · source · release history
  • Migrates JSON report schema to the new format in --format json output v0.20.0 · Oct 2021 · source · release history
  • AWS Security Hub integration via the security-hub output format for Trivy results v0.11.0 · Aug 2020 · source · release history

example

  • Export vulnerabilities in CycloneDX format for SBOM integration trivy image --format cyclonedx --output sbom.json aquasec/your-image:tag v0.24.0 · Feb 2022 · source
  • Render vulnerability reports as HTML emails for automated notification pipelines. trivy --format template --template "@/path/to/template" golang:1.12-alpine v0.4.3 · Jan 2020 · source
Vulnerability data enrichment shipped suggested Enriches scan results with additional vulnerability metadata such as CVSS vector strings, severity scores from various vendors, CWE identifiers, and direct advisory URLs. 6 releases · 1 other source · first seen May 2020

Suggested capability: Vulnerability database matching. This is our guess, not confirmed.

Also counts toward: JSON data export

release

  • SARIF report output now includes CVSS vectors for findings 0.65.0 · Jul 2025 · source · release history
  • Include CVSS v4 scores and vectors in scan results when available 0.58.0 · Dec 2024 · source · release history
  • Adds PrimaryURL field to the JSON output format for vulnerability entries v0.14.0 · Dec 2020 · source · release history
  • JSON output now includes CweIDs for each vulnerability entry v0.10.0 · Jul 2020 · source · release history
  • Includes CVSS vector strings and scores (NVD, RedHat) in JSON output v0.9.2 · Jul 2020 · source · release history
  • Adds VendorVectors field to JSON output containing raw CVSS v2/v3 strings for NVD and RedHat vendors v0.8.0 · May 2020 · source · release history

example

  • Extract the direct advisory link for a specific CVE from Trivy's JSON scan results. trivy image --format json alpine:3.10 | jq -r '.[0].Vulnerabilities[].PrimaryURL' v0.14.0 · Dec 2020 · source
Infrastructure scanning expansion shipped Adds support for scanning Azure Linux (Mariner) distributions and direct Ext2/Ext3 filesystems within VM contexts. 5 releases · first seen Jul 2024

release

  • trivy cloud subcommand is available for scanning cloud environments 0.68.0 · Dec 2025 · source · release history
  • AlmaLinux 10 is supported as a new platform for vulnerability scanning 0.65.0 · Jul 2025 · source · release history
  • Adds Ext2/Ext3 filesystem support in VM scanning module 0.55.0 · Sep 2024 · source · release history
  • Adds direct filesystem support in VM scanning module 0.55.0 · Sep 2024 · source · release history
  • Azure Linux support in Mariner database 0.54.0 · Jul 2024 · source · release history
Kubernetes cluster scanning shipped Scans a live Kubernetes cluster to surface vulnerabilities and misconfigurations across its workloads. 3 releases · 2 other sources · first seen Oct 2021

release

  • k8s: add support for controllers 0.61.0 · Mar 2025 · source · release history
  • Supports multi-container Kubernetes scans with accurate per-container misconfiguration reporting 0.57.0 · Oct 2024 · source · release history
  • Adds new networking API features to Ingress v0.20.2 · Oct 2021 · source · release history

example

  • Scan Kubernetes cluster with summary report trivy k8s --report summary cluster
  • Scan a Kubernetes cluster trivy k8s --report summary cluster
VEX format support expansion shipped Expands Vulnerability Exploitability Exchange (VEX) capabilities to include CSAF and OpenVEX formats, supporting dependency relationship modeling and non-root component mapping. 4 releases · first seen Jun 2024

release

  • Supports per-repo TLS configuration for VEX sources 0.69.0 · Jan 2026 · source · release history
  • Add initial support for loading external VEX files from SBOM references in CycloneDX reports 0.60.0 · Mar 2025 · source · release history
  • Improves CSAF VEX format support for dependency relationship modeling 0.52.0 · Jun 2024 · source · release history
  • Supports non-root components mapping to products in OpenVEX generation 0.52.0 · Jun 2024 · source · release history
Performance optimization via memory caching shipped Implements memory-based caching for scan data to reduce disk I/O overhead and improve subsequent scan performance. 3 releases · 1 other source · first seen Mar 2020

release

  • Enable concurrent access to the vulnerability database for performance improvement 0.68.0 · Dec 2025 · source · release history
  • Add memory cache backend to improve performance and reduce disk I/O overhead during scans 0.53.0 · Jul 2024 · source · release history
  • Changes internal cache storage to use a JSON-based format v0.5.0 · Mar 2020 · source · release history

example

  • Configure Trivy to use memory-based caching for faster subsequent scans without disk I/O overhead. trivy image --cache-backend memory myimage:latest 0.53.0 · Jul 2024 · source
License scanning expansion shipped Expands license scanning capabilities to support Go vendor directories, custom package type filtering, and Bun lock files. 4 releases · first seen May 2025

release

  • license scanner observes pkg_type option to filter by package type 0.65.0 · Jul 2025 · source · release history
  • Scan the vendor directory for licenses associated with go.mod files 0.63.0 · May 2025 · source · release history
  • Add a Bun lock file analyzer for Node.js dependencies 0.63.0 · May 2025 · source · release history
  • Support license scanning in both GOPATH and vendor directories for Go projects 0.63.0 · May 2025 · source · release history
Helm repository authentication shipped suggested Supports authentication and service name configuration for scanning private Helm repositories and managing Trivy service instances. 4 releases · first seen Mar 2022

Suggested capability: Credentialed vulnerability scanning. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Add plugin nested archive support for handling complex plugin packaging structures 0.53.0 · Jul 2024 · source · release history
  • Adds v9 pnpm lock file parser support for Node.js dependency analysis 0.52.0 · Jun 2024 · source · release history
  • Adds --helm.service-name flag to the Helm scan command to allow configuring the Trivy service name v0.24.3 · Mar 2022 · source · release history
  • Adds --helm.server-token flag to authenticate Helm repository access during scans v0.24.3 · Mar 2022 · source · release history
Private registry authentication shipped suggested Supports authentication mechanisms for private Docker registries using environment variables. 3 releases · 1 other source · first seen May 2019

Suggested capability: Container image vulnerability scanning. This is our guess, not confirmed.

release

  • Adds --tls-insecure-skip-verify flag to the client/server connection to disable TLS certificate validation v0.24.0 · Feb 2022 · source · release history
  • Supports TRIVY_REGISTRY_TOKEN environment variable for authenticating to private registries without username/password v0.8.0 · May 2020 · source · release history
  • Authentication for private Docker registries is supported using environment variables. v0.1.2 · May 2019 · source · release history

example

  • Enable TLS for the Trivy cache to connect to a secured Redis instance. export TRIVY_CACHE_REDIS_TLS_CERT=/path/to/cert.pem export TRIVY_CACHE_REDIS_TLS_KEY=/path/to/key.pem export TRIVY_CACHE_REDIS_TLS_CA=/path/to/ca.pem trivy image --cache-dir /tmp/trivy-cache… v0.23.0 · Jan 2022 · source
.NET self-contained deployment scanning shipped suggested Detects bundled runtimes in self-contained application deployments and scans them for CVEs alongside application dependencies. 2 releases · 1 other source · first seen Jun 2026

Suggested capability: Vulnerability database matching. This is our guess, not confirmed.

release

  • Detection of bundled runtimes in .NET self-contained deployments 0.72.0 · Jun 2026 · source · release history
  • Detects bundled .NET runtime in self-contained deployments, enabling CVE scanning of apps that ship their own runtime. v0.72.0 · Jun 2026 · source · release history

example

  • Audit a self-contained .NET binary or publish directory for vulnerabilities in the bundled runtime, not just your app dependencies. trivy fs --scanners vuln <path/to/self-contained-dotnet-publish/> v0.72.0 · Jun 2026 · source
Configuration and infrastructure authentication updates shipped Introduces JSON Schema validation for configuration files, custom TLS/certificate support for Helm and VEX sources, and stateless token handling for GitHub Apps. 2 releases · first seen Jan 2026

release

  • Support for new stateless format for GitHub App installation tokens 0.72.0 · Jun 2026 · source · release history
  • Adds JSON Schema for trivy.yaml configuration file via the flag feature 0.69.0 · Jan 2026 · source · release history
Advanced dependency resolution and mapping shipped Improves dependency analysis accuracy through Maven mirror support, Go version detection from ELF binaries, and tracking of the specific analyzer used for package detection. 2 releases · first seen Jan 2026

release

  • Detect Go version from ELF symbol table for binaries built with -trimpath 0.70.0 · Apr 2026 · source · release history
  • Adds AnalyzedBy field to track which analyzer detected packages 0.69.0 · Jan 2026 · source · release history
Language ecosystem detection expansion shipped suggested Extends vulnerability and dependency scanning support to new language ecosystems and package managers, including Julia, PyLock TOML (PEP 751), and Rocky Linux packages. 2 releases · first seen Jan 2026

Suggested capability: Vulnerability database matching. This is our guess, not confirmed.

Also counts toward: Scripting language support

release

  • Add pylock.toml (PEP 751) parser for Python dependency resolution 0.70.0 · Apr 2026 · source · release history
  • Enables vulnerability scanning for the Julia language ecosystem 0.69.0 · Jan 2026 · source · release history
Disk space management utilities shipped Provides commands to clean and remove Trivy data files, cache, images, and metadata to free up disk space on CI/CD runners. 1 release · 1 other source · first seen Jul 2024

Also counts toward: Command-line interface

release

  • Add clean subcommand to remove Trivy data files (cache, images, metadata) and free disk space 0.53.0 · Jul 2024 · source · release history

example

  • Remove Trivy cache and temporary files to free disk space on CI/CD runners after scans. trivy clean --all 0.53.0 · Jul 2024 · source
Server health monitoring shipped Provides health check endpoints and commands to verify the operational status of a running Trivy server instance. 1 release · 1 other source · first seen Oct 2020

release

  • Health check endpoint added to Trivy server at /healthz v0.12.0 · Oct 2020 · source · release history

example

  • Check the health status of a running Trivy server instance. curl http://127.0.0.1:4954/healthz v0.12.0 · Oct 2020 · source
Scan result integrity verification shipped Provides cryptographic verification of scan results to ensure data integrity. 1 release · first seen Sep 2025

release

  • Adds seal support for cryptographically verifying the integrity of Trivy scan results 0.67.0 · Sep 2025 · source · release history
Scan response relationship modeling shipped Includes dependency relationship metadata such as `workspaceRelationship` in scan results to clarify component dependencies. 1 release · first seen Dec 2024

release

  • Add workspaceRelationship to scan response JSON structure 0.58.0 · Dec 2024 · source · release history
Private registry profile management shipped Provides a dedicated command-line interface for managing cloud registry authentication profiles and service configurations. 1 release · first seen Oct 2024

Also counts toward: Command-line interface

release

  • Adds trivy registry subcommand for managing cloud registry authentication profiles 0.57.0 · Oct 2024 · source · release history
Custom detector support shipped Enables the use of custom detectors through configuration structs and fields to extend vulnerability detection capabilities. 1 release · first seen Jan 2022

release

  • Adds support for custom detectors via DetectorConfig struct and CustomDetectors field. v0.23.0 · Jan 2022 · source · release history
Single file scanning shipped suggested Allows scanning of individual application binary files directly via CLI command, rather than requiring a directory or image context. 1 other source · first seen Jan 2022

Suggested capability: Static application security testing. This is our guess, not confirmed.

Also counts toward: Command-line interface

example

  • Scan a single application binary file instead of a directory or image. trivy fs ./path/to/myapp.bin --security-checks vuln v0.23.0 · Jan 2022 · source

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 Trivy, 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 Trivy 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 →

Website history

trivy.dev, every change

Aqua Security's home page and 3 more pages as they looked each month from December 2021 to October 2026: 19 renders, 6 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Coverage

Missing something? Tell us

What Trivy connects to, runs on and detects, read from its release notes and docs. So far: 2 new supported platforms, 1 new vulnerability check.

Show

3 changes, tracked since Oct 5, 2026.

  • Oct 52026

    new Vulnerability detection for Echo-patched Python packages

    add vulnerability detection for Echo-patched Python packages (#10555)

    Source ↗

  • Oct 52026

    new Package classification for julia, bottlerocket, and centos stream

    classify julia, bottlerocket and centos stream packages (#11326)

    Source ↗

  • Oct 52026

    new uv workspace lockfile support

    With uv workspace lockfiles

    support uv workspace lockfiles (#10553)

    Source ↗

How we count

Read from 1 of 69 release notes and docs updates we hold for Trivy. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Trivy's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

69 entries

  1. October 20263
  2. June 20264
  3. April 20261
  4. January 20261
  5. December 20251
  6. September 20252
  7. July 20251
  8. June 20251
  9. May 20251
  10. April 20251
  11. March 20252
  12. January 20251
  13. December 20241
  14. October 20242
  15. September 20241
  16. July 20242
  17. June 20241
  18. April 20224
  19. March 20222
  20. February 20222
  21. January 20221
  22. December 20213
  23. November 20211
  24. October 20213
  25. July 20211
  26. May 20211
  27. April 20211
  28. February 20211
  29. December 20202
  30. November 20201
  31. October 20201
  32. August 20201
  33. July 20202
  34. June 20201
  35. May 20202
  36. March 20202
  37. February 20201
  38. January 20201
  39. December 20192
  40. November 20192
  41. October 20191
  42. August 20191
  43. June 20191
  44. May 20192
    Show
    Coverage in all entries

    69 entries

    Project health

    Issue, contributor and maintainer activity in aquasecurity/trivy, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 96 ±0 vs prior 12 months
    2. Maintainers 3 +1 joined · −3 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 84% of issues opened, last 12 months
    5. Median time to close 4.8 days first maintainer reply 44 hours
    6. Open backlog 170 of 3,134 issues ever filed
    1. Issues opened / month 13 · 0 communitymaintainers
    2. Open backlog 170
    3. Contributors / month 12
    4. Commits / month 41
    5. Stars 37,971
    Issue themes, last 12 months
    • bugs 40%
    • features 21%
    • docs 2%
    • other 37%

    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

    Security incidents

    Times attackers got a poisoned Trivy release out under the project's name. We can't see which version or image you run, so check each one against your installs, image digests and CI logs.

    A hijacked release pipeline shipped a credential-stealing Trivy, and poisoned its GitHub Actions

    Confirmed Contained Replacement release available

    On March 19, 2026 attackers used stolen credentials to publish Trivy v0.69.4, force-push 76 of the 77 version tags of aquasecurity/trivy-action and replace all seven tags of aquasecurity/setup-trivy. The poisoned Actions ran a credential stealer before the real scan. On March 22 they pushed two more Trivy images, 0.69.5 and 0.69.6, straight to Docker Hub. Aqua says it removed the malicious artifacts and that the attack continued one that began in late February, after credential rotation that was not done all at once. The stolen credentials were later used against other projects, including LiteLLM.

    What was affected

    WhereWhatVersions or tagsWhen
    GitHub Releases aquasecurity/trivy binaries, deb and rpm packages v0.69.4 Mar 19, 2026, 18:22 to 21:42 UTC
    Live for about three hours. Aqua also lists the "latest" tag during this window.
    GHCR, ECR Public and Docker Hub Trivy container images 0.69.4, latest Mar 19, 2026, 18:22 to 21:42 UTC
    Same window as the binaries.
    Docker Hub aquasec/trivy 0.69.5, 0.69.6, latest Mar 22, 2026, 15:43 UTC to Mar 23, 2026, 01:40 UTC
    Pushed directly to Docker Hub with separately stolen credentials. No GitHub tag or release existed for either version.
    GitHub Actions aquasecurity/trivy-action 0.0.1 to 0.34.2 Mar 19, 2026, 17:43 UTC to Mar 20, 2026, 05:40 UTC
    Any version tag except 0.35.0. Aqua dates the start from the earliest suspicious activity in its audit log. A workflow pinned to a commit from before 2025-04-09 also pulled in a poisoned setup-trivy.
    GitHub Actions aquasecurity/setup-trivy v0.2.0 to v0.2.6 Mar 19, 2026, 17:43 to 21:44 UTC
    Any use that was not pinned to a commit.

    Not affected, per Trivy

    • Trivy v0.69.3 and earlier, binary or image.
    • Images referenced by digest, and binaries built from source.
    • The official Homebrew formula, which builds from source.
    • trivy-action 0.35.0, and workflows pinned to a commit made after 2025-04-09.

    What Trivy says to do

    1. Search CI logs for runs from March 19 to 20 that used trivy-action or setup-trivy by version tag, and for any use of Trivy v0.69.4, 0.69.5 or 0.69.6.
    2. Look in your GitHub organization for a public repository named tpcp-docs, which the stealer creates when it cannot send data out.
    3. Treat every secret a matching runner could read as stolen and rotate it.
    4. Move to Trivy v0.69.3 or v0.69.2, trivy-action 0.35.0 or setup-trivy v0.2.6, and pin Actions to a full commit hash, not a tag.

    Sources: Aqua Security: Trivy ecosystem supply chain temporarily compromised (CVE-2026-33634) ↗ · Wiz: Trivy Compromised, everything you need to know ↗ · checked Nov 1, 2026

    Articles

    5 articles · updated Nov 4, 2026

    Where Trivy turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.

    • Getting Started with Trivy: A Must-Have Tool for DevSecOps TecAdmin
      And if you’re looking for a tool to make that happen without breaking a sweat, let me introduce you to Trivy.
      2 more quotes
      Why Trivy Matters for DevSecOps First things first: why should you care about Trivy?
      Trivy fits right into that mindset.
    • Containers Vulnerability Scanner: Trivy Hacking Articles
      This article talks about Trivy, which is a simple and comprehensive vulnerability scanner for containers and other artifacts, suitable for Continuous Integration and Testing.
      2 more quotes
      Furthermore, with its ease of usage, Trivy can simply be integrated into the CI/CD pipeline (DevSecOps) by installing and adding the binary to the project.
      In addition, Trivy offers complete visibility across programming language and operating system packages and has a wide database of vulnerabilities, which allows quick scans of critical CVEs.

    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 →