Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 5 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Semgrep, Inc. · semgrep.dev

Compare with Snyk → Report an error on this page Is this your product? →

Link to this page

Semgrep: AI-assisted analysis on whats-best.ai Semgrep: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Semgrep at a glance

Vendor
Semgrep, Inc.
Headquarters
Incorporated in the United States source, captured 6 Nov 2026
Data hosting
Outside the EU by default; pages mention the United States source, captured 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates Semgrep 3.5/5, the mean of 6 judges. Semgrep is a SAST, supply-chain and secrets platform, strongest on developer workflow, where five of six judges scored 8: findings arrive as PR and MR comments with in-thread triage, merge-blocking policies and an autofix that opens a draft pull request in 2 to 10 minutes. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Semgrep alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Application Security Engineer

Weighted verdict

Application security engineer at a payments company in Frankfurt with 120 developers, two of them security champions per team, under PCI DSS and DORA. Wants taint analysis that follows user input across files, reachability so the backlog holds only vulnerable code that is actually called, secrets checked for validity across the whole git history, push protection, custom rules for in-house frameworks, and reports an auditor accepts.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Application Security Engineer

Panel median The Application Security Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Application Security Engineer
Code analysis (SAST & code quality) 4 of 5 4 of 5
Dependencies (SCA), licences & secrets 4 of 5 4 of 5
Developer workflow, quality gates & fixes 4 of 5 3.5 of 5
Platforms, deployment & administration 3.5 of 5 3 of 5
Source-code handling, security & compliance 3.5 of 5 3.5 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 3 of 5 2.5 of 5

Code analysis (SAST & code quality)

How this is scored

What the tool finds in the company's own code: static application security testing with data-flow and taint analysis across functions and files, the languages and frameworks covered and at what depth, the rule sets (OWASP Top 10, CWE, custom rules), bugs and code smells, duplication, cyclomatic and cognitive complexity, maintainability and technical-debt measures, test coverage import, infrastructure-as-code checks, and how false positives are measured and kept down.

0 — Does not analyse source code; a dependency, secret or runtime scanner only, or a different kind of product.

3 — Pattern-based rules or linters for a handful of languages; data-flow analysis, the rule list, quality metrics and false-positive handling are basic or not described.

5 — SAST for the common languages (Java, JavaScript/TypeScript, Python, C#, Go, PHP) with the rule list published and mapped to OWASP and CWE, bugs and code smells, duplication and complexity metrics, coverage import, and custom rules or rule configuration documented.

8 — Cross-file taint analysis with the supported frameworks listed per language, a rule language customers can write in, infrastructure-as-code checks, maintainability or code-health scores over time, false-positive rates or benchmarks published, and each finding explained with its data flow and a fix.

10 — Analysis a large polyglot codebase relies on: deep interprocedural analysis across many languages with the depth stated per language, independent benchmark results, quality and security trends per team and hotspot, and every rule documented with examples and its precision.

Report an error

The Application Security Engineer

Cross-file taint analysis is documented per language with source-to-sink traces and the interfile engine behind a pro flag, coverage is stated per language with Pro rule counts and framework-specific control flow for Java, JavaScript and TypeScript, Terraform checks are generally available, and the rule language is deep enough to encode our in-house frameworks. What holds it below the top: the false-positive figures are the vendor's own claims ('80% fewer false positives', 'up to 3.5x more true positives at 19% lower cost per true positive versus AI alone') rather than independent benchmarks, and we found no public information on quality metrics such as complexity, duplication or technical debt. 1 2 5 6 14 15

Report an error

Dependencies (SCA), licences & secrets

How this is scored

What comes from outside or should never be committed: software composition analysis of direct and transitive dependencies with the ecosystems and lockfiles supported, the vulnerability database and how quickly it is updated, reachability analysis, licence detection and policies, SBOM export (CycloneDX, SPDX), malicious and typosquatted package detection, end-of-life components, automatic upgrade pull requests, container image scanning, and secret detection in code and git history with the number of detectors, validity checks and revocation guidance.

0 — No dependency or secret scanning of any kind.

3 — Known-vulnerability alerts for dependencies in one or two ecosystems or a basic secret pattern check; transitive dependencies, licences, SBOMs and git history are basic or not described.

5 — SCA for the main ecosystems including transitive dependencies, licence detection with policies, SBOM export in a standard format, upgrade suggestions or pull requests, and secret detection in commits with the detector list described.

8 — Reachability analysis that shows whether vulnerable code is called, malicious-package detection, the vulnerability database and its sources documented, end-of-life components flagged, secrets checked for validity and scanned across the full git history, and push protection that stops a secret before it lands.

10 — Supply-chain coverage a regulated software maker can file: every ecosystem the company builds with, reachability for each, SBOM and VEX output for customers, licence obligations explained per licence, secrets found outside git (tickets, chat, containers) with automated revocation, and the database's coverage and latency evidenced.

Report an error

The Application Security Engineer

Reachability analysis is generally available for eleven ecosystems and written into the SBOM as a state and justification — exactly what keeps a backlog holding only code that is actually called — with malicious dependency detection, EPSS, licence policies per category with allow/block decisions, and autofix pull requests that upgrade vulnerable dependencies. Secrets detection covers 630+ credential types with semantic and entropy analysis, validity checks against services like AWS, Slack and GitHub performed locally so the secret never leaves my infrastructure, and pre-commit hooks that stop a leak before it lands; historical scanning of the git history is documented but marked beta, and we found no public information on end-of-life component flagging or container image scanning. 3 6 8 15 16 18

Report an error

Developer workflow, quality gates & fixes

How this is scored

Whether developers see and act on the findings where they work: pull and merge request comments and status checks, quality gates that block a merge on new issues, a focus on new code against a baseline, IDE plugins with the same rules as the server, CLI and CI integrations (GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines), pre-commit hooks, triage, suppression and ignore rules with reasons, deduplication, fix suggestions and AI autofix with the model behind it, and scan times.

0 — Findings only in a separate report; no pull request, IDE or CI integration.

3 — A CI step or a dashboard of findings; pull request comments, gates, IDE plugins and triage are basic or not described.

5 — Pull or merge request comments and status checks on the common platforms, a configurable quality gate that can fail a build, a new-code baseline, IDE plugins for the common editors, CI integrations documented, and findings that can be ignored or marked as false positives.

8 — IDE results that match the server rules, gates per branch or project with thresholds per severity, pre-commit or push-time checks, deduplicated findings across tools, fix suggestions or AI autofix as a reviewable change with the model provider stated, and typical scan times documented.

10 — A workflow that keeps noise low on a large team: findings routed to the owning team, every suppression audited with a reason and expiry, autofix with its acceptance rates published, and the gate's behaviour on every supported platform documented with its limits.

Report an error

The Application Security Engineer

Developers get PR and MR comments on GitHub, GitLab, Bitbucket and Azure with reply-to-triage commands and named reasons, diff-aware scans against a baseline, remediation policies that can block a merge and are overridable only with permissions, noise control so only rules meeting severity criteria comment, IDE plugins for VS Code and JetBrains, and AI autofix opening a reviewable draft PR in 2 to 10 minutes with the model provider named as Amazon Bedrock and Anthropic Claude. Held below the top because we found no public information on whether the IDE plugins run the same rules as the server, whether suppressions carry an expiry, or deduplication of findings across tools. 5 8 18 19 21 22

Report an error

Platforms, deployment & administration

How this is scored

How the tool fits the company: the code hosts supported (GitHub, GitLab, Bitbucket, Azure DevOps) cloud and self-managed, a self-hosted or on-premise edition or a scanner that runs inside the customer's network, a documented REST API and webhooks, issue tracker integrations (Jira), single sign-on (SAML or OIDC) and SCIM, roles and permissions per project and team, portfolio reports across repositories, audit logs, export of findings (SARIF, CSV), and partner or multi-organisation accounts.

0 — One repository at a time with no integrations and no administration.

3 — A web dashboard and one code host; the API, roles, SSO and self-hosted options are basic or not described.

5 — GitHub, GitLab and Bitbucket or Azure DevOps supported, a documented REST API, Jira integration, roles per organisation and project, single sign-on, reports across repositories, and export of findings in a standard format.

8 — Self-managed code hosts supported, a self-hosted edition or an in-network scanner documented, SCIM provisioning, audit logs, granular roles per team, portfolio dashboards with trends, SARIF import and export, and webhooks for findings.

10 — Administration that scales across many teams and business units: every setting reachable by API with parity stated, an air-gapped deployment documented, SSO enforced with SCIM, audit logs exportable to a SIEM, and multi-organisation or partner management.

Report an error

The Application Security Engineer

The platform documents PR checks across GitHub, GitLab, Bitbucket and Azure, self-managed hosts including Bitbucket Data Center and on-prem source code management at the enterprise tier, an OpenAPI-documented REST API with a stable v1 and a v2 under development, Jira integration, webhooks, Slack, SSO via OIDC and SAML, and audit logs of every scan and remediation. It sits mid-scale because we found no public information on SCIM provisioning, granular roles per team, SARIF or CSV export of findings, or a self-hosted edition of the platform itself, though the CLI does run scans on customer-controlled infrastructure. 1 7 8 9 20 21 22

Report an error

Source-code handling, security & compliance

How this is scored

What the vendor does with the customer's source code and how it holds up in an audit: whether code leaves the customer's network or only results do, where and how long code and findings are stored, whether code or findings are used to train AI models and how to opt out, encryption, the vendor's own certifications (ISO 27001, SOC 2) with their scope, a stated availability or SLA and a public status page, audit logs, and reports mapped to OWASP, CWE, PCI DSS, ISO 27001 or the EU Cyber Resilience Act.

0 — Nothing on how source code is handled, secured or retained.

3 — A security page with general claims; code retention, AI training, certifications and the status page are basic or not described.

5 — How source code is accessed and whether it is stored is described, encryption in transit and at rest, SOC 2 or ISO 27001 stated, a public status page, a statement on whether code trains AI models, and compliance reports mapped to OWASP or CWE.

8 — Code retention periods stated, an option where code never leaves the customer's network, AI features documented with their model provider and an opt-out, certifications with scope and reports available on request, an SLA published, and reports mapped to several standards including PCI DSS or the Cyber Resilience Act.

10 — Source-code handling evidenced end to end: a data-flow diagram of what is sent where, zero retention options, independent audits published with scope, AI processing that can run on the customer's own models, and compliance evidence an auditor can export without asking the vendor.

Report an error

The Application Security Engineer

SOC 2 Type II is certified with the report period stated (December 1, 2023 to November 30, 2024) and downloadable from a trust-centre portal, dedicated pages map the product to ISO 27001:2022 Annex A controls and SOC 2 criteria with audit logs capturing every scan, finding and remediation with timestamps and user attribution, and the pages state plainly that Semgrep Inc. is not itself ISO 27001 certified. For a PCI DSS shop the gaps are concrete: we found no public information on PCI DSS or Cyber Resilience Act report mappings, no stated retention period for source code (two years is stated only for personal information), no published SLA, and the terms grant a perpetual licence to use customer data to improve and develop Semgrep products and services. 9 12 13 22 23

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where source code, findings, SBOMs, account and usage data are stored and processed, and who the subprocessors are (hosting, AI models used for autofix and triage, vulnerability data sources, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Public vulnerability databases and package registries the scanner queries are part of what the product does and are not counted against it; where the customer's code and findings are stored and who processes them is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (AI models, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps code and findings on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The Application Security Engineer

The contracting entity is Semgrep, Inc., a Delaware corporation governed by California law, with servers stated to be in the United States on AWS, WorkOS for authentication, OpenAI as the default Multimodal provider and AWS Bedrock for the Assistant — an entirely US chain for the hosted platform, softened by a published subprocessor list, a data processing agreement, a data transfer impact assessment and GDPR statements in the trust centre. The open-source CLI can scan locally without a login, which keeps code on my own servers, but the platform's findings, triage and AI features are US-hosted. 4 9 12 13 23

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per developer, contributor, committer or line of code and per plan, how contributors are counted, what the free tier and open-source plan include, which scanners (SAST, SCA, secrets, containers) and features (SSO, self-hosting, AI autofix, compliance reports) cost extra, limits on repositories, scans or lines of code, minimum seats, monthly versus annual terms, and VAT.

0 — No public prices at all; every customer is a sales call.

3 — A starting price exists, but how developers or lines of code are counted and what the add-ons cost is unclear.

5 — Plans are public with their price per developer or per lines of code and main inclusions, but at least one commonly needed piece (SSO, self-hosting, an extra scanner, AI autofix or the enterprise tier) is unpriced or "contact sales".

8 — Every plan priced publicly with its counting rule (active contributors, lines of code) explained, scanners and add-ons priced, limits on repositories and scans stated, a free or open-source tier with its limits, and monthly and annual terms and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of developers, repositories and lines of code, with every scanner, add-on, self-hosted licence and support level priced and the cancellation and data-export terms published.

Report an error

The Application Security Engineer

The pricing page publishes a free edition (up to 10 repositories, maximum 10 contributors) and Teams starting at $30/month per contributor with Code at $30/month/contributor, Supply Chain at $30/month/contributor and Secrets at $15/month/contributor, SSO included, repository limits per tier and AI credit allowances of 60 free and 20 per developer per month on Teams. I still cannot compute a real annual cost for 120 developers: the enterprise tier with volume pricing, on-prem source code management support and custom CI/CD carries no public price, and we found no public information on how a contributor is counted, annual versus monthly terms, VAT treatment, or the cost of AI credits beyond the allowance. 8

Report an error

European sovereignty — proven facts

5 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Outside the EU unverified
Why unverified?

The statement covers the website/Services servers; the CLI can also run scans locally so source code need not leave the customer's machine, but anything hosted by Semgrep is in the US.

0/4 pts 13 Report an error
Hosting options Self-hostable unverified
Why unverified?

Only the OSS Engine/CLI can be self-hosted; the Semgrep AppSec Platform itself is a SaaS-only offering, with Enterprise offering merely optional deployment in dedicated (Semgrep-run) infrastructure.

1/1 pts 12 Report an error
Open source Open source (copyleft) unverified
Why unverified?

The LGPL 2.1 applies to the Semgrep OSS Engine only; the same terms describe the Semgrep AppSec Platform Service and Pro rules as proprietary.

1/1 pts 12 Report an error
Data processing agreement On request unverified
Why unverified?

The DPA is only listed as a document inside the Trust Portal behind the 'Get access' / 'Ask for information' gate, so these excerpts show no self-serve way to view or conclude it online.

0/1 pts 9 Report an error
Transfer impact assessment Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error

Questions about Semgrep

Is Semgrep European?

No. whats-best.ai classifies Semgrep as Rest of world. Its vendor, Semgrep, Inc., is incorporated in the United States, per the vendor’s page captured 6 Nov 2026.

Where does Semgrep store data?

Semgrep stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026. The vendor’s pages mention the United States as hosting location, per the vendor’s page captured 6 Nov 2026.

Does Semgrep have a free plan?

Yes. Semgrep has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to Semgrep?

As of 19 Nov 2026, the panel rates SonarQube (3.5/5), Aikido Security (3.5/5) and Endor Labs (3.5/5) highest among the other 18 Code Security & Quality (SAST/SCA) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is SonarQube (EU origin, foreign-owned, Switzerland). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Semgrep alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (23)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage semgrep.dev Checked 6 Nov 2026 Details →
  2. 2 Features page (SAST) semgrep.dev Checked 6 Nov 2026 Details →
  3. 3 Features page (secrets) semgrep.dev Checked 6 Nov 2026 Details →
  4. 4 Features page (open-source edition) semgrep.dev Checked 6 Nov 2026 Details →
  5. 5 Integrations page semgrep.dev Checked 6 Nov 2026 Details →
  6. 6 Documentation docs.semgrep.dev Checked 6 Nov 2026 Details →
  7. 7 API documentation docs.semgrep.dev Checked 6 Nov 2026 Details →
  8. 8 Pricing page semgrep.dev Checked 6 Nov 2026 Details →
  9. 9 Trust centre trust.semgrep.dev Checked 6 Nov 2026 Details →
  10. 10 Public status page status.semgrep.dev Checked 6 Nov 2026 Details →
  11. 11 About page semgrep.dev Checked 6 Nov 2026 Details →
  12. 12 Terms of service semgrep.dev Checked 6 Nov 2026 Details →
  13. 13 Privacy policy semgrep.dev Checked 6 Nov 2026 Details →
  14. 14 Code analysis (SAST & code quality) — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  15. 15 Code analysis (SAST & code quality) — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  16. 16 Dependencies (SCA), licences & secrets — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  17. 17 Dependencies (SCA), licences & secrets — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  18. 18 Developer workflow, quality gates & fixes — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  19. 19 Developer workflow, quality gates & fixes — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  20. 20 Platforms, deployment & administration — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  21. 21 Platforms, deployment & administration — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  22. 22 Source-code handling, security & compliance — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →
  23. 23 Source-code handling, security & compliance — found from sitemap docs.semgrep.dev Checked 6 Nov 2026 Details →