Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Trivy is an open-source scanner from Aqua Security that finds vulnerabilities, misconfigurations, exposed secrets, and licence issues across container images, filesystems, repositories, and clusters.

What Is Trivy?
Trivy is an open-source security scanner from Aqua Security, written in Go and distributed as a single binary under the Apache 2.0 licence. One command scans a container image, a directory, a git repository, a virtual machine image, or a running Kubernetes cluster, and it looks for four different classes of problem at once: known vulnerabilities in packages, misconfigurations in infrastructure code, exposed secrets, and licence obligations.
That breadth is deliberate and is why it has become the default scanner in a great many pipelines. Tools that each solve one of those problems require four integrations, four report formats, and four sets of suppression rules.
trivy image --severity HIGH,CRITICAL --ignore-unfixed --exit-code 1 acme/api:1.4.2
Three flags carry most of the practical weight. --severity narrows output to what you intend to act on. --exit-code 1 makes the pipeline fail. And --ignore-unfixed hides vulnerabilities for which no fixed version exists yet, which is the difference between a list of actions and a list of facts — a base image routinely contains a dozen unfixable low-severity issues that no amount of rebuilding will resolve.
Trivy identifies operating system packages from Alpine, Debian, Ubuntu, Red Hat, Amazon Linux, SUSE, Photon, and others, and language dependencies for npm, Python, Go, Java, Ruby, PHP, Rust, .NET, and more, including dependencies compiled into Go and Rust binaries where no manifest is present.
trivy config ./infrastructure checks Terraform, CloudFormation, Kubernetes manifests, Helm charts, and Dockerfiles. This engine is the one absorbed from tfsec, which Aqua is consolidating into Trivy.trivy fs --scanners secret ./src looks for exposed credentials, complementing a dedicated tool such as Gitleaks in the commit path.trivy k8s --report summary cluster scans a live cluster’s workloads.trivy image --format cyclonedx --output sbom.json produces a software bill of materials, in CycloneDX or SPDX, which Trivy can also scan later without the original image.The Trivy Operator takes this into the cluster itself, scanning workloads continuously and publishing results as Kubernetes custom resources, so a security report is something you query with kubectl rather than export from a dashboard.
The first is the vulnerability database. Trivy downloads it as an OCI artefact from a public registry, and that registry applies rate limits. A busy pipeline running dozens of scans an hour from a shared network address will eventually start failing on database downloads rather than on findings. Mirror the database into your own registry and set TRIVY_DB_REPOSITORY, or cache it between runs.
The second is noise during adoption. The first scan of a mature image produces hundreds of findings, most of them unfixable and low severity, and the usual reaction is to disable the step. Begin with critical severity and fixed vulnerabilities only, get that to zero, then widen. Persistent exceptions belong in .trivyignore or a trivyignore.yaml with an expiry date and a stated reason, not in a pipeline flag.
The closest open-source comparison is Grype and Syft, which split inventory generation from vulnerability matching into two composable tools. Trivy does more in one binary and is easier to adopt; the Anchore pair fits better into an SBOM-centred process where the inventory is a first-class artefact. Commercial platforms such as Snyk add central reporting, reachability analysis, and support, which matters more as the number of repositories grows than as the number of scanners does.
For UK organisations, a scheduled image scan with results feeding a patching process is the straightforward way to evidence the Cyber Essentials expectation that high and critical vulnerabilities are addressed within 14 days of a fix being available, and it is the control auditors most often ask to see for container security.
Yes. Trivy is open source under the Apache 2.0 licence with no feature gating, no account, and no scan limits, and the full vulnerability database is publicly available. Aqua Security sells a commercial platform that adds central management, runtime protection, and reporting across an estate, but the scanner itself is complete and widely used in production without any paid component.
It hides vulnerabilities that have no fixed version available from the package maintainer. Those findings are real but not actionable, and they typically make up most of the output for a mature base image. Filtering them produces a list a team can work through. Review them separately on a schedule, because a previously unfixable issue becomes actionable the moment a patch is published.
Because the database is pulled from a public container registry that enforces rate limits, and a pipeline making many scans from the same network address exhausts them. Mirror the database into your own registry and point Trivy at it with the database repository environment variable, or cache the database directory between pipeline runs. This is the single most common operational complaint about the tool.
Trivy if you want one tool covering vulnerabilities, misconfigurations, secrets, and licences with minimal integration effort. Grype paired with Syft if you want to treat the software bill of materials as a durable artefact that you sign, store, and re-scan later against new vulnerability data. Both are well maintained and free, and the choice is mostly about how your pipeline is organised.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.