Do coding agents recommend Trivy?
Trivy was chosen in 3% of 460 judged security testing sessions, ranking sixth. Measured with Claude Code, Codex, Grok Build CLI and Muse Code.
Trivy was chosen in 3% of 460 judged security testing sessions, ranking sixth. It was also raised as a candidate in 48 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Grok Build CLI and Muse Code had to solve a problem in security testing inside a realistic codebase. Not what a chat assistant says about Trivy. What an agent actually installed.
The numbers
| Category | Security testing |
| Sessions in the category | 460 |
| Sessions where Trivy was chosen | 14 |
| Install share | 3% |
| Rank in category | 6 of 65 |
| Codebases it won in | 3 |
| Raised as a candidate, not chosen | 48 |
| Chosen when considered | 23% |
| Site | trivy.dev |
By agent
With 14 wins spread across 4 agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose Trivy | Share |
|---|---|---|---|
| Claude Code | 116 | 5 | 4% |
| Codex | 116 | 1 | 1% |
| Grok Build CLI | 116 | 4 | 3% |
| Muse Code | 112 | 4 | 4% |
What Trivy was up against
The full ranking in security testing, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | ZAP | 111 | 24% |
| 2 | Semgrep | 78 | 17% |
| 3 | SonarQube | 66 | 14% |
| 4 | Burp Suite | 30 | 7% |
| 5 | GitHub Advanced Security | 25 | 5% |
| 6 | Trivy (this page) | 14 | 3% |
| 7 | StackHawk | 12 | 3% |
| 8 | Strix | 11 | 2% |
What this means
This is an integration problem, not a presence problem. Agents raised Trivy in 48 sessions and chose it in 14, so it reaches the shortlist and then loses. Something at the last step is costing the session, and in our data that is usually a quickstart that does not run when pasted, documentation describing an interface that changed, or a package name that does not match the product name.
That is the cheaper of the two problems to have. The reason is written down in each losing transcript.
Where these numbers come from
The 460 sessions in security testing are part of a published set of 15,000, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every security testing run can be replayed on the board.
If you work on Trivy: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Trivy?
Yes. Trivy was chosen in 14 of the 460 judged sessions in security testing, a 3% install share, ranking sixth in its category.
Does Claude Code recommend Trivy?
In 5 of the 116 sessions in security testing run with Claude Code, which is 4%.
Do different coding agents treat Trivy differently?
Not much. Claude Code, Codex, Grok Build CLI and Muse Code chose it at similar rates, between 1% and 4% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Trivy considered but not chosen?
It was raised as a candidate in 48 sessions without being chosen, and chosen in 14. That is a 23% conversion from considered to chosen.
Where this comes from
Armature ran 15,000 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.