Semgrep vs Dependabot
Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.
Entry price
From $30 per contributor/month (Teams, per product)
Free tierFree
FreeWhat drives the bill
The metric that actually scales your invoice.
The CLI plus community rules costs nothing and covers a lot. Teams is priced per product per contributor — Code $30, Supply Chain $30, Secrets $15 — so scanning for all three multiplies the per-contributor figure.
Completely free. Advanced Security features such as code scanning are separately licensed.
Free tier
Open-source CLI is free and complete; hosted platform free for up to 10 contributors.
Free on all GitHub repositories including private ones.
Open source
LGPL-2.1 (CLI)
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Widely used
Semgrep · since 2020
Category standard
GitHub (Microsoft) · since 2017
Strengths
- Custom rules are genuinely writable — you can encode your own security or architecture standards in an afternoon.
- Free CLI with a large community rule registry is immediately useful.
- Fast enough to run on every pull request without complaint.
- Free and requires a single config file to enable.
- Version-bump pull requests mean remediation is a review, not a task.
- Grouped updates keep the PR volume manageable.
Limitations
- Pattern matching without full dataflow misses some vulnerability classes.
- Community rule quality is uneven; expect to curate.
- Advanced dataflow and supply-chain features are paid only.
- No reachability analysis, so it reports vulnerabilities in code you never call.
- PR noise is a genuine problem on large dependency trees without grouping configured.
- GitHub only.
Best for
Teams that want customisable static analysis and can start entirely for free.
Every GitHub repository, as the free baseline before considering a paid SCA tool.
All of these integrate with: GitHub.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.