Do coding agents recommend OWASP Dependency-Check?
OWASP Dependency-Check was chosen in 1% of 671 judged security testing sessions, ranking number 12.
OWASP Dependency-Check was chosen in 1% of 671 judged security testing sessions, ranking number 12. It was also raised as a candidate in 23 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 OWASP Dependency-Check. What an agent actually installed.
The numbers
| Category | Security testing |
| Sessions in the category | 671 |
| Sessions where OWASP Dependency-Check was chosen | 8 |
| Install share | 1% |
| Rank in category | 12 of 85 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 23 |
| Chosen when considered | 26% |
| Site | owasp.org |
By agent
With 8 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 OWASP Dependency-Check | Share |
|---|---|---|---|
| Claude Code | 187 | 0 | 0% |
| Codex | 256 | 4 | 2% |
| Grok Build CLI | 116 | 2 | 2% |
| Muse Code | 112 | 2 | 2% |
What OWASP Dependency-Check was up against
The full ranking in security testing, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | ZAP | 155 | 23% |
| 2 | Semgrep | 103 | 15% |
| 3 | SonarQube | 83 | 12% |
| 4 | Burp Suite | 44 | 7% |
| 5 | GitHub Advanced Security | 30 | 4% |
| 6 | Trivy | 27 | 4% |
| 7 | Strix | 23 | 3% |
| 8 | Hurl | 15 | 2% |
What this means
OWASP Dependency-Check was raised in 23 sessions and chosen in 8. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough.
Where these numbers come from
The 671 sessions in security testing are part of a published set of 15,561, 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 OWASP Dependency-Check: 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 OWASP Dependency-Check?
Yes. OWASP Dependency-Check was chosen in 8 of the 671 judged sessions in security testing, a 1% install share, ranking number 12 in its category.
Does Claude Code recommend OWASP Dependency-Check?
In 0 of the 187 sessions in security testing run with Claude Code, which is 0%.
Do different coding agents treat OWASP Dependency-Check differently?
Not much. Claude Code, Codex, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 2% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 110 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 OWASP Dependency-Check considered but not chosen?
It was raised as a candidate in 23 sessions without being chosen, and chosen in 8. That is a 26% conversion from considered to chosen.
Where this comes from
Armature ran 15,561 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.