GitGuardian

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by GitGuardian SAS · www.gitguardian.com

Compare with GitHub Advanced Security → Report an error on this page Is this your product? →

Link to this page

GitGuardian: AI-assisted analysis on whats-best.ai GitGuardian: 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.

GitGuardian at a glance

Vendor
GitGuardian SAS
Headquarters
Incorporated in France source, captured 6 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates GitGuardian 3/5, the mean of 6 judges. Judged on its own pages, GitGuardian is a secrets-detection platform rather than a broad code analyser. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

GitGuardian alternatives, European ones first →

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

The Platform Engineer

Weighted verdict

Platform engineer at an insurer in Hanover who runs a self-managed GitLab and Jenkins for 300 developers inside the company network; source code may not leave it. Wants a self-hosted edition or a scanner that runs in the pipeline and sends only results, SAML and SCIM from Entra ID, an API to roll scan settings out to 900 repositories, SARIF output, audit logs, and upgrades that do not break the pipelines.

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

Scored by The Platform Engineer

Panel median The Platform 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 Platform Engineer
Code analysis (SAST & code quality) 0 of 5 0 of 5
Dependencies (SCA), licences & secrets 3 of 5 3.5 of 5
Developer workflow, quality gates & fixes 3 of 5 3.5 of 5
Platforms, deployment & administration 4 of 5 4 of 5
Source-code handling, security & compliance 3.5 of 5 4 of 5
European sovereignty 4 of 5 4 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 Platform Engineer

Everything captured describes a secrets-detection engine — 550+ specific detectors, generic high-entropy patterns, four billion commits analysed — and the page titled SAST for GitHub defines itself as detecting hardcoded credentials in real time. We found no public information on taint or data-flow analysis, rule sets mapped to OWASP or CWE, or quality measures such as complexity, duplication and technical debt, so on this criterion the product is a different kind of tool. 1 15 16

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 Platform Engineer

On the secrets side this is as deep as it gets: 550+ detectors plus generic and custom ones, scans across the entire git history, validity checks with non-intrusive HTTP calls, pre-commit and pre-receive blocking, a stated 91% true-positive rate, and secrets hunted in Slack, Jira, Confluence, containers and on developer laptops with rotate-and-revoke guidance. We found no public information on dependency composition analysis, licence policies or SBOM export, so the criterion as a whole cannot reach the top levels. 1 3 4 6 16 19

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 Platform Engineer

ggshield slots into our world exactly: pre-commit, pre-push and pre-receive hooks plus eight CI systems including Jenkins, GitLab CI/CD and GitHub Actions, with the scan addable as a required status check that blocks a merge and fails the workflow on a leak. Triage with severity scoring, saved views, Jira and ChatOps routing, developer feedback links and a 91% true-positive rate address the noise question; we found no public information on documented scan times, per-branch gate thresholds, or suppression rules with reasons. 3 4 6 19 20

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 Platform Engineer

The self-hosted edition is properly documented — Helm or KOTS onto bare metal, private cloud or our own Kubernetes cluster, with self-hosted API base URLs spelled out — which is my non-negotiable for keeping source code inside the company network. SAML2 single sign-on has step-by-step setup for Microsoft Entra ID, SCIM provisioning with just-in-time onboarding and deprovisioning, forced SSO, audit logs over dashboard and API actions, and a documented REST API including a scan route; we found no public information on SARIF export, which I would need to roll results across 900 repositories. 3 4 7 8 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 Platform Engineer

The data-handling pages are concrete enough for an audit conversation: only the patches of commits with detected secrets are collected, retention periods are stated, all customer data is removed at the end of the service relationship, encryption is TLS 1.2 or greater and AES-256-CBC or greater, and SOC 2 Type II has been maintained since 2022 with annual audits by Prescient Assurance. A public status page, 48-hour incident notification and a compliance framework list including PCI DSS and ISO 27001 are there; we found no public information on a published SLA, or on the model provider behind the AI features and any opt-out. 10 14 23 24

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 Platform Engineer

Contracting is with GitGuardian SAS at 54 rue de Seine in Paris under French law with the CNIL as lead supervisory authority, the EU SaaS runs in Frankfurt on AWS eu-central-1, a data processing addendum and a subprocessors page are published, and the self-hosted edition keeps code and findings on our own servers — which is the deployment I would run. A US region and a US affiliate exist, with Standard Contractual Clauses covering the transfers; the captured pages do not show each subprocessor with its location. 3 10 12 13 14 23 24

Report an error

Pricing transparency not rated — the vendor publishes no price

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 Platform Engineer

The Starter free plan is documented down to its limits — up to 25 devs, unlimited real-time scanning, up to 500 historical-scan detections, 10K API calls per month — and the seat basis is explained as read access to VCS members for billing. Above that we found no public information on prices: Growth is 'Contact sales', and there is no public figure from which an annual cost for 300 developers could be computed. 1 8 23

Report an error

European sovereignty — proven facts

3 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 Not determined unverified
Why unverified?

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

— uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

Pricing lists self-hosted deployment only under the Enterprise plan ("Self-hosted deployment + GitGuardian Bridge"), so it is not available on Starter or Growth.

1/1 pts 8 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

Only the link title on the legal index page is shown; the excerpt does not contain the agreement text or an online acceptance flow.

1/1 pts 12 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about GitGuardian

Is GitGuardian European?

Yes. whats-best.ai classifies GitGuardian as EU-Made. Its vendor, GitGuardian SAS, is incorporated in France, per the vendor’s page captured 6 Nov 2026.

Where does GitGuardian store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

Does GitGuardian have a free plan?

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

What are the best alternatives to GitGuardian?

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: GitGuardian 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 (24)

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

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