Small business▼−1Since September 2026: 5% → 4%, −1 point. Inside the 11-point floor: within noise. Read over the models both editions asked.
4%from 5% in September 2026
Inside the floor by 10 pointsRank 3 → 5 of 44
GitHub · 1 category · RankedGitHub Dependabot
53Judge labels
7First choices
10Negative labels
12 / 14Models named it
1Category
October 2026 Edition. Every number here is derived from the raw labels under vendor table v2026-10.8, every buyer segment counted.
Best standing
8% in SCA for mid-market buyers
Rank 6 of 50 in the mid-market standingaccepted challenger
0 of 14 models made it the first choice on the direct prompt; 18% of its 17 labels there were negative.
What the models named instead of GitHub Dependabot →By buyer segmentRead the same way at every buyer size.
Small business4 of 49
5%28 labels
accepted challenger
Mid-market6 of 50
8%17 labels
accepted challenger
Enterprise51 of 56
0%7 labels
under the label threshold
In sca · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading
Standing by category
Every category where a model named GitHub Dependabot for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.
| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Software composition analysis | Developer platform | 8% | 6 of 50 | 18% | 17 | accepted challenger | =heldSince September 2026: 5% → 5%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
Movement
Since September 2026, GitHub Dependabot held within the floor in its one category: no change cleared 11 points.
Best category · SCA · by segment
Mid-market=heldSince September 2026: 5% → 5%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
5%from 5% in September 2026
Inside the floor by 11 pointsRank 5 → 6 of 43
Enterprise=heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
0%from 0% in September 2026
Inside the floor by 11 pointsRank 46 → 22 of 47
All categories · Mid-market
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| SCA | 5% | 5% | =heldSince September 2026: 5% → 5%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 5 → 6 of 50 |
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
By model
How each model treated GitHub Dependabot across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.ShowHide
By model
How each model treated GitHub Dependabot across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.
ShowHide| 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 | 1 | 1 | 1 | 0 | 3 |
| Perplexity Sonar | 0 | 1 | 0 | 1 | 2 |
| Grok 4.20 | 0 | 0 | 0 | 1 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 1 | 1 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 1 | 0 | 1 |
| Kimi K2 | 0 | 2 | 0 | 0 | 2 |
| GLM 4.7 FlashX | 1 | 0 | 0 | 0 | 1 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 1 | 1 | 0 | 1 | 3 |
| Muse Glimmer 30B | 1 | 0 | 1 | 0 | 2 |
By framing
Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.
FramingLabels by classFirst choices
Direct6 labelsNone
Paraphrase8 labelsNone
Comparative10 labels3not counted in share
Budget-constrained17 labels7
Scale-constrained2 labelsNone
Negative10 labels1not counted in share
First choiceAlternativeMentionNegative53 labels in all, every segment counted; 7 of the 11 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.
What the models said for it
Verbatim evidence the judge attached to positive labels.
“GitHub Dependabot is the zero-excuse baseline: dependency alerts and automated update PRs free on every repo” Muse Glimmer 30B · SCA · budget prompt · first choice
“Best low-budget starting point: GitHub Dependabot if your code is already on GitHub.” GPT-6 Luna · SCA · budget prompt · first choice
“the best place to start is GitHub Dependabot (if you're on GitHub) or Trivy” GLM 4.7 FlashX · SCA · budget prompt · first choice
“If your team is already using GitHub, Dependabot is the clear winner.” Gemini 3.5 Flash · SCA · budget prompt · first choice
And against it
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.
“Useful for alerts, but sources warn about false positives, limited transitive analysis, and limited remediation automation in this basic form.” Perplexity Sonar · SCA · negative prompt · soft negative
“a reasonable choice for GitHub-based dependency alerts and updates, but don't assume it gives complete coverage of your software supply chain” GPT-6 Luna · SCA · negative prompt · soft negative
“Free/native, but basic (no deep reachability/licenses), prone to stale alerts” Grok 4.20 · SCA · negative prompt · soft negative
Named alongside
The products named in the same answers as GitHub Dependabot, over the 53 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and GitHub Dependabot was named but was not.ShowHide
Named alongside
The products named in the same answers as GitHub Dependabot, over the 53 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and GitHub Dependabot was named but was not.
ShowHideProductSame answerTook the first choice insteadHead to head
A head-to-head page exists where both products are among a category's top eight. The other rows are the same fact without a page behind them, so they link to the product instead.
What carried it into the answer
The sites and pages cited by the answers that named GitHub Dependabot. A fact about retrieval, not a lever on the model.
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 51 of the 53 answers that named GitHub Dependabot and are not a share of its labels.
Domains cited
appsecsanta.com26
guideflow.com25
dupple.com20
endorlabs.com20
safeguard.sh18
aikido.dev17
sonatype.com17
expertinsights.com14
blog.jetbrains.com13
checkmarx.com13
183 of the 183 domain citations in answers naming GitHub Dependabot came from somebody else's page.
Pages cited
Pages are listed as the models cited them.
Search and answers
Where GitHub Dependabot stands in Google search beside where it stands in the models' answers.ShowHide
Search and answers
Where GitHub Dependabot stands in Google search beside where it stands in the models' answers.
ShowHideIn search
Google, US estimates- Searches for its name, Google
- 720 a month (“github dependabot”)
- AI search demand for its name, est.
- 54 a month
- Its own site
- It sits on GitHub's site (github.com), so there are no site figures for it alone
In answers
This editionShare of first choices
8%
rank 6 of 50 in SCA
Segment leader
31%
Trivy
- First choices
- 7 across its categories
- Named in
- 53 answers
- Its own site cited
- in 51 of the answers that named it
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.
Names read as GitHub Dependabot
What the judge wrote, as written, with how often. The vendor table decides that these count as GitHub Dependabot; a claim can dispute any of them.
Dependabot 5GitHub Advanced Security / Dependabot 2GitHub Dependabot / GitHub Code Security 1
Follow GitHub Dependabot
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.
The company
GitHub is the company behind GitHub Dependabot.ShowHide
The company
GitHub is the company behind GitHub Dependabot.
ShowHideOn record
Company recordsIn its own words
Stated by the vendor, not checked- Certifications
- ISOSOC 2GDPR
- Customers named
- SAPOtto GroupSPH MediaPostmates
- Not stated on the pages read
- Positioning, who it is for, price, starting price, free plan or trial, integrations, hosting
What GitHub Dependabot's own pages state, read October 5, 2026: github.com/security, securitylab.github.com/secure-code-game, github.com/features/code-quality, github.com/resources/articles, securitylab.github.com/resources/secure-code-game. A claimed page can correct any of them.
Is this your product?
Claim this page
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 GitHub Dependabot'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 GitHub Dependabot, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
What a new claim receivesHide what a new claim receives
A new claim receives the current edition's vendor brief for GitHub Dependabot by email, built from the raw record of the edition. It shows:
- where GitHub Dependabot is named, by buyer and by framing, and which cells hold its first choices;
- the claims the models make when they name it, ranked, with the strongest and the weakest quoted;
- its vocabulary against the segment leader's, and the pages the models cited;
- who was chosen in the answers that did not name GitHub Dependabot, and every reason the record gives;
- a battlecard for each top rival: the head-to-head split, why they win, and the reservation quoted against them;
- one page of published figures cleared to show a buyer.