| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Static application security testing | Developer platform | 36% | 1 of 71 | 5% | 63 | endorsed leader | ▼−17Since September 2026: 47% → 30%, −17 points. Past the 11-point floor: movement. Read over the models both editions asked. |
| Software composition analysis | Developer platform | 2% | 11 of 50 | 0% | 6 | under 10 labels · led by Trivy at 31% | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Application security posture management | Developer platform | 0% | 26 of 70 | 0% | 3 | under 10 labels · led by Aikido Security at 37% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| SAST | 47% | 30% | ▼−17Since September 2026: 47% → 30%, −17 points. Past the 11-point floor: movement. Read over the models both editions asked. | Moved past the floor | Rank 1 of 71, unchanged |
| SCA | 0% | 2% | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 23 → 11 of 50 |
| ASPM | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 26 of 70, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 1 | 0 | 1 | 1 | 3 |
| GPT-5.4 mini | 1 | 1 | 0 | 0 | 2 |
| Gemini 3.5 Flash | 3 | 2 | 1 | 0 | 6 |
| Perplexity Sonar | 1 | 1 | 1 | 0 | 3 |
| Grok 4.20 | 1 | 4 | 0 | 0 | 5 |
| Mistral Small | 1 | 2 | 2 | 0 | 5 |
| DeepSeek V4 Flash | 3 | 3 | 2 | 0 | 8 |
| Llama 4 Maverick | 1 | 0 | 3 | 0 | 4 |
| Qwen 3.7 Flash | 2 | 3 | 1 | 0 | 6 |
| Kimi K2 | 4 | 3 | 0 | 0 | 7 |
| GLM 4.7 FlashX | 2 | 2 | 1 | 0 | 5 |
| MiniMax M2.5 | 1 | 3 | 0 | 0 | 4 |
| GPT-6 Luna | 4 | 1 | 0 | 1 | 6 |
| Muse Glimmer 30B | 2 | 3 | 2 | 1 | 8 |
Verbatim evidence the judge attached to positive labels.
“Semgrep as the primary scanner across all languages... For most budget-constrained companies, Semgrep OSS + SonarQube Community Edition... is the most commonly recommended starting point” Muse Glimmer 30B · SAST · budget prompt · first choice
“Tools like Semgrep are generally preferred for modern CI/CD because they are lightweight, customizable, and run significantly faster.” GLM 4.7 FlashX · SAST · negative prompt · first choice
“look for developer-friendly alternatives like Semgrep, where rules are written in YAML and read like standard code” Gemini 3.5 Flash · SAST · negative prompt · first choice
“The most common pattern among practitioners is using Snyk for SCA (dependency scanning) + Semgrep for SAST” MiniMax M2.5 · SAST · comparative prompt · first choice
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.
“Semgrep OSS and Bandit are fast and low false-positive for obvious patterns, but miss vulnerabilities that span multiple functions... insufficient as sole nightly security scanners” Muse Glimmer 30B · SAST · negative prompt · soft negative
“Semgrep Community Edition as your only deep security scanner: It can be useful for fast checks and custom rules, but its analysis is limited to a file/function context” GPT-6 Luna · SAST · negative prompt · soft negative
“Checkmarx, Veracode, and Semgrep have all struggled with this because their rule-based engines flag anything that could be a vulnerability” Claude Haiku 4.5 · SAST · 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 194 of the 208 answers that named Semgrep and are not a share of its labels.
715 of the 715 domain citations in answers naming Semgrep 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.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Conference or event | 369 | undated | SAST, SCA | ||
| Blog | 316 | undated | SAST, SCA | ||
| Glossary or explainer | 37 | undated | |||
| Case study | 19 | undated | |||
| Comparison | 11 | undated | |||
| Webinar or virtual event | 8 | undated | SAST | ||
| Template or tool | 2 | undated | |||
| Report or ebook | 1 | undated | |||
| News or press | 1 | undated |
As the event pages on semgrep.dev state them, read September 28, 2026.
Every page semgrep.dev exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read September 29, 2026.
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 Semgrep's own pages state, read September 28, 2026: semgrep.dev, semgrep.dev/pricing, trust.semgrep.dev, semgrep.dev/products/pro-engine, semgrep.dev/case-studies. 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 Semgrep'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 Semgrep, 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 Semgrep by email, built from the raw record of the edition. It shows:
AI models recommend Semgrep first in Static application security testing this edition. Each badge says so in the buyer's words, names the edition, and links to the standing. The next edition issues a new badge; this one stays true as a record of October 2026.
Badges read on light and dark pages. Alt text carries the claim, the category, the edition and the index, so it stays a citation where the image does not load.