Trivy
Ranked 4 of 10 vulnerability scanners by recommenders
Open-source scanner that checks container images, code and configs for known vulnerabilities; people recommend it for automated security scanning, though its 2026 GitHub Actions compromises drew heavy criticism.
Open-source scanner that checks container images, code and configs for known vulnerabilities; people recommend it for automated security scanning, though its 2026 GitHub Actions compromises drew heavy criticism.
33 people gave an opinion
- recommend it
- 10
- criticize it
- 23
- approval share
- 30%
Recommended in 5 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 10 people recommend itNeeds 10 or more, met.
- 0.4 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Scans container images for vulnerabilities
“Tools like trivvy make it possible to do the scans”
Comment from 3 Aug 2026 in “Critical CVE issued for hallucinated SQLite vulnerability” “automated image scanning with Trivy”
Comment from 8 Mar 2026 in “A Decade of Docker Containers” Seen as core security tooling
“built in vulnerability and configuration scanning so you don't get pwned by Trivy”
Comment from 1 May 2026 in “Shai-Hulud Themed Malware Found in the PyTorch Lightning AI Training Library” “tools like trivy and sempreg are basically the backbone of every safe program”
Comment from 7 May 2026 on Hacker News
What people warn about
Each mark is one comment
Repeated supply chain compromises
“it was a direct attack on Trivy, exploiting components that Aqua had full control and responsibility for”
Comment from 22 Mar 2026 on Hacker News “the fault was within the side of ironically a security product that they used called Trivy”
Comment from 6 Jul 2026 in “Mark Zuckerberg tells staff that AI agents haven't progressed enough” “Any system with Trivy 0.69.4 on it (and being run) can be assumed to be compromised.”
Comment from 20 Mar 2026 in “Aquasecurity/Trivy GitHub Repository and Homebrew Cask Compromised (again)” - Comment from 3 Aug 2026 in “Critical CVE issued for hallucinated SQLite vulnerability”
- Comment from 4 Oct 2026 in “Run Qwen 3.8 Flash Next (125B) on consumer hardware (RTX 4090) at 100T/s”
- Comment from 21 Mar 2026 in “Attempts to post the latest Trivy security incident have been marked [dead]”
- Comment from 23 Mar 2026 in “Trivy Under Attack Again: Widespread GitHub Actions Tag Compromise Secrets”
Slow or incomplete incident response
“they are going to continue to fail to protect their own artifacts and distribution chains”
Comment from 22 Mar 2026 on Hacker News “they're clearly not capable of handling this and should be enlisting outside help”
Comment from 23 Mar 2026 in “Trivy Under Attack Again: Widespread GitHub Actions Tag Compromise Secrets” “the first rotation didn't fully revoke access. the attacker walked right back in”
Comment from 23 Mar 2026 in “Trivy Under Attack Again: Widespread GitHub Actions Tag Compromise Secrets” - Comment from 25 Mar 2026 in “Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised”
- Comment from 22 Mar 2026 on Hacker News
Unpinned and mutable dependencies
“the action itself can still make mutable decisions (like pulling the “latest” version of a binary from somewhere on the internet)”
Comment from 22 Mar 2026 on Hacker News “even pinned actions themselves download unpinned transitive dependencies”
Comment from 30 Apr 2026 in “GitHub Actions is the weakest link”
Other vulnerability scanners people recommend
The four most recommended other vulnerability scanners, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| OpenAI Codex Security | 21 | 30 | 41% | 4 | — | — |
| govulncheck | 13 | 0 | 100% | 9 | — | Approved |
| AISLE | 11 | 2 | 85% | 5 | — | Approved |
| TrivyThis page | 10 | 23 | 30% | 5 | — | — |
| cargo-vet | 8 | 0 | 100% | 5 | — | — |
What people said
31 of the 35 comments that mention it, newest first. Each links to the original comment.
“Even security companies (see trivy supply chain attack) get these badly wrong.”
“had two supply chain compromises within a month of each other earlier this year”
“Tools like trivvy make it possible to do the scans”
“the fault was within the side of ironically a security product that they used called Trivy”
“tools like trivy and sempreg are basically the backbone of every safe program”
“built in vulnerability and configuration scanning so you don't get pwned by Trivy”
“even pinned actions themselves download unpinned transitive dependencies”
“trivy images get compromised, like last week”
“the initial vulnerability in Trivy was introduced by some clawbot”
“the Trivy ecosystem got turned into a credential stealer”
“Trivy is also bad here but the blast radius should have been more limited.”
“69.3 isnt safe. The safe thing to do is remove all trivy access.”
“a security scanner that cant secure its own credentials”
“Trivy got turned into a supply chain attack nightmare”
“I don't think Trivy is bad software and I use it at work.”
“just because they got pwned (twice, or once, but really badly”
“the first rotation didn't fully revoke access. the attacker walked right back in”
“You're supposed to scan for vulnerabilities, not become one!”
“they're clearly not capable of handling this and should be enlisting outside help”
“their Docker images have now been compromised”
“Sounds like Trivy is still compromised”
“it was a direct attack on Trivy, exploiting components that Aqua had full control and responsibility for”
“They did a lot of what you describe, although perhaps not well enough.”
“the action itself can still make mutable decisions (like pulling the “latest” version of a binary from somewhere on the internet)”
“they failed to successfully remediate and contain the damage”
“they are going to continue to fail to protect their own artifacts and distribution chains”
“Maybe it was intentionally compromised all along.”
“Trivy (a very widely-used security scanner) was recently compromised.”
“Any system with Trivy 0.69.4 on it (and being run) can be assumed to be compromised.”
“automated image scanning with Trivy”
“Existing SBOM tools (Trivy, Syft, Grype) don't catch any of this.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.