Tool profilesBased on official documentation, not tested by us

Trivy: scan your containers, code folders and dependencies for known vulnerabilities, free and open source

Trivy is a free command-line scanner from Aqua Security that checks container images, folders, git repositories and Kubernetes for known vulnerabilities, misconfigurations, secrets and licences. Based on the official README and release page, not tested by us: what it does, its limits and what we could not confirm.

Type

Vulnerability and misconfiguration scanner (command line)

License and cost

Apache-2.0 licence, free

Reviewed

3 Nov 2026

Version

v0.76.1 (release page shows 21 October, no year; the page footer shows 2026)

Best for

Teams that ship containers or infrastructure files and want a free check for known vulnerabilities, mistakes in configuration and leaked secrets before they deploy.

Watch out for

A clean scan is not proof of safety: it only finds what is already known and covered. Canary builds are not for production.

← All tool profilesNo. 5 / 11

In one sentence

Trivy is a scanner you run on something you are about to ship, such as a container image, a project folder, a git repository or a Kubernetes cluster. It reports known vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary in the software and libraries it finds, mistakes in configuration files (infrastructure as code), secretsSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary left in files and software licences.

Who it is for

Founders and small teams who build with containers, Docker or cloud configuration files, often with help from AI assistants, and want a cheap check before each release. It is a command-line tool, so you need to be comfortable typing commands.

What the documentation says

Everything below comes from the project's README and release page, which we read on 3 November 2026.

  • What it scans (targets): container images, local filesystems, remote git repositories, virtual machine images and Kubernetes clusters.
  • What it looks for (scanners): operating-system packages and software dependencies (including producing a software bill of materials), known CVEs, misconfigurationsMisconfiguration A setting left wrong or at its default that exposes something, such as a storage bucket open to everyone or an admin page with no login. Tap again to open the glossary in infrastructure-as-code files, secrets and sensitive data, and software licences.
  • Coverage: the README says it supports most popular languages, operating systems and platforms, and points to a separate coverage page. We did not read that page.
  • Install: Homebrew (brew install trivy), a Docker image (docker run aquasec/trivy), or a binary from the releases page. The documentation lists more options.
  • Basic use: the README gives the shape trivy <target> [--scanners ...] <subject>, with examples such as trivy image python:3.4-alpine, trivy fs --scanners vuln,secret,misconfig myproject/ and trivy k8s --report summary cluster.
  • Who maintains it: Aqua Security. The README says Aqua's commercial products build on Trivy.
  • Latest release we saw: v0.76.1. Its notes say it includes mitigations for a certificate-authority key compromise (the intermediate CA of a provider named eMudhra), built with a Go version that includes a related fix, and that its container images ship an updated trust store. The maintainers recommend upgrading and redeploying container images.

The good

  • Free, Apache-2.0 licence, from an established security company.
  • One tool for several jobs: vulnerabilities, configuration mistakes, secrets and licences.
  • It scans things at the point you ship them: images, folders and repositories.
  • The documentation covers filtering results, reports, caching, air-gapped use and generating a software bill of materials.

The limits it admits

  • The README warns that canary builds, generated on each push to the main branch, may have critical bugs and are not recommended for production.
  • The README gives no detail on how the vulnerability database is downloaded or kept up to date. That matters for offline or locked-down environments, and we did not read the database pages of the documentation.

When not to use it

  • If you think a clean result means your software is safe. It reports what is already known and covered, nothing more.
  • As your only check. Patching, access control and review still matter.
  • If you want a hosted dashboard with teamwork features: Trivy is a command-line tool, and Aqua's paid products are separate.

What it costs you

Time more than money. The README gives no estimate of setup time. The real work comes after: deciding which severities to act on, fixing or accepting each finding, adding the scan to your build pipeline and keeping the tool itself up to date. We have not measured any of this.

Typical setup mistakes

  • Scanning once and forgetting. New vulnerabilities are found every day. A scan from last month says nothing about today.
  • Never failing the build. A pipeline that does not stop on findings lets a known vulnerability ship. Check the documented option for the exit code.
  • Ignoring findings without a note. An ignore list with no reason and no expiry hides risk.
  • Running an old Trivy. The tool needs updates too, as the latest release notes show.
  • Scanning only your own code. Most findings are in dependencies and in the base image.

How to check that it works

Official documentation and our approach, not something we ran: scan a small test project or a public image you do not depend on, and expect a list of findings. Then scan a clean, minimal image and compare. Never test on a production system or with real keys.

Where to start

We did not test the tool, so we do not offer a tutorial. Follow the official documentation: httpsHTTPS The secure version of the web address protocol: it encrypts what travels between a visitor and your site and checks that the site is the real one. Tap again to open the glossary://trivy.dev/docs/latest/

What we could not confirm

We did not download, install or run Trivy, so everything above is the project's own description. We did not read the vulnerability-database pages, the coverage list, the exit-code and ignore-file pages or the code. The release page showed v0.76.1 with the date 21 October and no year. We do not know how many false alarms it gives, how fast it is on a large image, or how it compares with other scanners.

Glossary: vulnerability, CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary, supply chainSupply chain attack An attack that reaches you through something you already trust and install, such as a code package, a tool or a provider. Tap again to open the glossary, patchPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary. See also our OSV-Scanner profile for dependency checks.

More free tools

Other profiles in this section.

Sources

Follow us

New profiles and security news: YouTube (@safet2ship) and Instagram (@safet2ship).

YouTube channel · Instagram

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks