| Category | Function | Share | Rank | Negative rate | Labels | Quadrant |
|---|---|---|---|---|---|---|
| Static application security testing | Developer platform | 0% | 47 of 47 | 52% | 23 | criticized challenger |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 1 | 1 | 0 | 2 |
| GPT-5.4 mini | 0 | 0 | 0 | 1 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 2 | 2 |
| Perplexity Sonar | 0 | 0 | 1 | 1 | 2 |
| Grok 4.1 Fast | 0 | 0 | 3 | 1 | 4 |
| Mistral Small | 0 | 0 | 2 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 0 | 1 | 2 | 3 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 4 | 4 |
| Kimi K2 | 0 | 0 | 1 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 1 | 0 | 0 | 1 |
| MiniMax M2.5 | 0 | 0 | 0 | 1 | 1 |
Verbatim evidence the judge attached to positive labels.
“Coverity and Fortify are legacy heavyweights, often chosen for their ability to handle massive, multi‑language codebases” GLM 4.7 FlashX · SAST · comparative prompt · alternative
“For broadest language coverage, Checkmarx and Fortify lead.” Claude Haiku 4.5 · SAST · comparative 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.
“High-cost, legacy platforms (like OpenText Fortify or older on-premise setups of Checkmarx)... Avoid legacy, binary-upload scanners and heavyweight on-premise engines.” Gemini 3.5 Flash · SAST · negative prompt · hard negative
“Why Legacy Tools (Veracode, Checkmarx, Fortify) are Usually Wrong for Mid-Market B2B” Gemini 3.5 Flash · SAST · direct prompt · hard negative
“Tools to Avoid on a Tight Budget ... Fortify” Qwen 3.7 Flash · SAST · budget prompt · hard negative
“Traditional Fortify configurations and older Checkmarx deployments ... only detect what their rule authors anticipated ... mature but limited” DeepSeek V4 Flash · SAST · negative prompt · soft negative
Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 73 of the 89 answers that named OpenText Fortify and are not a share of its labels.
389 of the 389 domain citations in answers naming OpenText Fortify came from somebody else's page.
Pages are listed as the models cited 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 OpenText Fortify'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 OpenText Fortify, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at opentext.com is approved on the spot, any other address is reviewed by hand.
Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.