From the experiment

Do coding agents recommend HCL AppScan?

HCL AppScan was chosen in 4% of 181 judged security platforms sessions, ranking fifth. Measured with Claude Code, Codex, Grok Build CLI and Muse Code.

Published October 14, 2026 Updated November 18, 2026 Read as Markdown

HCL AppScan was chosen in 4% of 181 judged security platforms sessions, ranking fifth. It was also raised as a candidate in 11 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 platforms inside a realistic codebase. Not what a chat assistant says about HCL AppScan. What an agent actually chose.

One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about security platforms in general, and the splits below cannot separate the two. Treat them as a description of that repository.

The numbers

CategorySecurity platforms
Sessions in the category181
Sessions where HCL AppScan was chosen8
Install share4%
Rank in category5 of 27
Codebases it won in1
Raised as a candidate, not chosen11
Chosen when considered42%
Sitehcltechsw.com

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.

AgentSessionsChose HCL AppScanShare
Claude Code5124%
Codex7234%
Grok Build CLI30310%
Muse Code2800%

What HCL AppScan was up against

The full ranking in security platforms, from the same sessions:

#ProductRuns wonShare
1Checkmarx One5028%
2GitLab Security4324%
3Snyk2212%
4Aikido Security1910%
5HCL AppScan (this page)84%
6GitHub Advanced Security + ZAP63%
7DefectDojo + Gitleaks + Semgrep + Trivy + ZAP53%
8GitHub Advanced Security + Microsoft Defender for Cloud32%

What this means

HCL AppScan was raised in 11 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 181 sessions in security platforms 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 platforms run can be replayed on the board.

If you work on HCL AppScan: 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 HCL AppScan?

Yes. HCL AppScan was chosen in 8 of the 181 judged sessions in security platforms, a 4% install share, ranking fifth in its category.

Does Claude Code recommend HCL AppScan?

In 2 of the 51 sessions in security platforms run with Claude Code, which is 4%.

Do different coding agents treat HCL AppScan differently?

Not much. Claude Code, Codex and Grok Build CLI chose it at similar rates, between 4% and 10% 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 HCL AppScan considered but not chosen?

It was raised as a candidate in 11 sessions without being chosen, and chosen in 8. That is a 42% 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.

Read next

All library pages