| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Application security posture management | Developer platform | 0% | 22 of 70 | 22% | 9 | under 10 labels · led by Aikido Security at 37% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 1 | 1 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 0 | 1 | 1 | 2 |
| Mistral Small | 0 | 0 | 1 | 0 | 1 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 1 | 1 | 0 | 2 |
| Kimi K2 | 0 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 2 | 0 | 0 | 2 |
| GPT-6 Luna | 1 | 0 | 0 | 0 | 1 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“start with ArmorCode and Veracode Risk Manager” GPT-6 Luna · ASPM · comparative prompt · first choice
“Checkmarx or Veracode: If you are looking for a more traditional, enterprise-grade solution” MiniMax M2.5 · ASPM · paraphrase prompt · alternative
“The Best for Compliance-Heavy Industries: Veracode (Hyland)” Qwen 3.7 Flash · ASPM · paraphrase prompt · alternative
“Good for earlier-stage AppSec programs” MiniMax M2.5 · ASPM · budget prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“It's not overly enterprise-heavy like Checkmarx or Veracode” Grok 4.1 Fast · ASPM · paraphrase prompt · soft negative
“Veracode acquiring Longbow Security” Gemini 3.5 Flash · ASPM · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 32 of the 35 answers that named Veracode Risk Manager and are not a share of its labels.
159 of the 159 domain citations in answers naming Veracode Risk Manager came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Veracode Risk Manager's own pages state, read October 5, 2026: veracode.com/risk-manager, veracode.com/veracode-risk-manager-latam, veracode.com/veracode-risk-manager-brazil, veracode.com/manage-web-app-attack-surface-risk, docs.veracode.com/r/VRM_APIs. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Veracode Risk Manager's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Veracode Risk Manager, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Veracode Risk Manager by email, built from the raw record of the edition. It shows: