GitHub Advanced Security

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 4 of 6 dimensions proven

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

by GitHub, Inc. · github.com

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

Link to this page

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

GitHub Advanced Security at a glance

Vendor
GitHub, Inc.
Headquarters
Incorporated in the United States source, captured 6 Nov 2026
Data hosting
Outside the EU by default; pages mention the EU and Australia 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 GitHub Advanced Security 3/5, the mean of 6 judges. GitHub Advanced Security adds CodeQL code scanning, Dependabot dependency alerts and secret scanning to the GitHub platform. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

GitHub Advanced Security 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) 2 of 5 2 of 5
Dependencies (SCA), licences & secrets 3.5 of 5 3.5 of 5
Developer workflow, quality gates & fixes 3 of 5 3 of 5
Platforms, deployment & administration 3.5 of 5 4 of 5
Source-code handling, security & compliance 3.5 of 5 3.5 of 5
European sovereignty 3 of 5 2.5 of 5
Pricing transparency 3 of 5 3 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

CodeQL is documented as "industry-leading semantic code analysis" for security vulnerabilities and coding errors, with Copilot Autofix covering "90% of alert types in JavaScript, Typescript, Java, and Python", multi-repository variant analysis and a preview scanner for AI-application risks. But we found no public information on the published rule set, OWASP or CWE mapping, taint-analysis depth, complexity or maintainability metrics, or how false positives are handled, so I cannot place it at the fully documented SAST level. 5 8 2 14

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

Dependabot detects vulnerabilities and raises grouped automated pull requests, with prioritization by exploitation likelihood, severity, triage rules, runtime context and reachability analysis in public preview, plus SBOM export and artifact attestations up to SLSA Build Level 3. Secrets are the strongest part: full Git history on all branches, validity checks against the issuing service, push protection, custom and generic patterns, AI-detected secrets and a 150+ provider partner program. We found no public information on licence detection and policies, malicious-package detection, end-of-life components or the vulnerability database's sources. 15 8 6 3

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

Default setup applies security settings to every repository from one configuration and rulesets stop merges that add high-severity alerts, push protection blocks secrets before they land, alerts auto-close on fix and can be tracked with issues, and third-party analysis tools can run inside Actions or in an external CI system — which is the hook my Jenkins pipelines would use. Copilot Autofix delivers reviewable fixes in four languages. We found no public information on IDE plugins matching server rules, ignore or suppression rules with reasons, deduplication across tools, or typical scan times. 2 5 8 20 3

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

This is close to my checklist: a REST API for code scanning alerts on API version 2026-03-10, webhooks, SARIF interoperability with third-party tools, SAML single sign-on with SCIM provisioning from the enterprise features, an Audit Log API, an enterprise account managing multiple organizations, and a GitHub Enterprise Server tier named in the licence plans alongside the cloud one. Default setup rolling one configuration to every repository speaks directly to my 900-repository rollout. The FAQ addresses Azure DevOps, and we found no public information on pointing the scanners at a self-managed GitLab — for me that gap is the difference between adopting and admiring. 7 5 8 2 1

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

Private repository contents are treated as confidential, SOC1 and SOC2 type 2 reports are produced annually, FedRAMP Tailored ATO is stated, a Data Protection Agreement is published, and the status page shows per-service uptime with a 90-day history. The terms grant a licence to train AI models on content unless you opt out through account settings or run under a customer or volume agreement, and the AI inference subprocessors are at least named. We found no public information on encryption specifics, compliance reports mapped to OWASP, CWE or PCI DSS, or a documented deployment where code never leaves the customer's network — the one thing my compliance team would ask first. 11 12 8 13 10 9

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

The contracting entity is GitHub, Inc. of San Francisco with GitHub B.V. in Amsterdam named as a controller, and Enterprise Cloud offers an EU data residency option on Microsoft Azure — but by default personal data is stored in a variety of locations including the United States and shared with affiliates including Microsoft. The subprocessor list is published with locations and shows the whole chain — hosting on AWS, Azure, GCP and Oracle, AI inference on OpenAI, Anthropic, xAI, Cerebras and Fireworks, support on Zendesk — almost entirely in the United States, with SCCs and Data Privacy Framework certification as the stated safeguards. A US parent with US AI providers and an opt-in EU region is not a chain my data protection officer will sign off on without heavy argument. 12 13 8

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

The two security add-ons carry public per-committer prices — "Code Security... $ 30 USD per active committer/month" and "Secret Protection... $ 19 USD per active committer/month" — on top of platform tiers priced at "$ 0 USD", "$ 4 USD per user / month" and "$ 21 USD per user / month", with free-tier limits, a 30-day trial, price locked during the payment term and 30 days' notice of changes. How an "active committer" is counted, the price of the self-hosted Enterprise Server tier, support levels and VAT treatment are not on the captured pages, and code scanning consumes GitHub Actions minutes — a cost driver named but not quantified, which makes my annual budget only partly computable. 20 8 5 11

Report an error

European sovereignty — proven facts

4 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?

Enterprise Cloud customers can buy an EU data residency option (S7) and some subprocessors process data in the EU (S11), but by default customer data is stored in a variety of locations including the United States.

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

Self-hosting is offered only via the separately licensed GitHub Enterprise Server product, not the standard cloud plans, which can also select an EU data residency region.

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

The excerpt only links to the standard DPA rather than reproducing it, and it is framed around organization-provided accounts and Enterprise customers.

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

Questions about GitHub Advanced Security

Is GitHub Advanced Security European?

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

Where does GitHub Advanced Security store data?

GitHub Advanced Security stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026. The vendor’s pages mention the EU and Australia as hosting locations, per the vendor’s page captured 6 Nov 2026.

Does GitHub Advanced Security have a free plan?

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

What are the best alternatives to GitHub Advanced Security?

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: GitHub Advanced Security 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 (20)

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

  1. 1 Vendor homepage (product page) github.com Checked 6 Nov 2026 Details →
  2. 2 Features page (Code Security) github.com Checked 6 Nov 2026 Details →
  3. 3 Features page (Secret Protection) github.com Checked 6 Nov 2026 Details →
  4. 4 Documentation docs.github.com Checked 6 Nov 2026 Details →
  5. 5 Documentation (code scanning) docs.github.com Checked 6 Nov 2026 Details →
  6. 6 Documentation (secret scanning) docs.github.com Checked 6 Nov 2026 Details →
  7. 7 API documentation docs.github.com Checked 6 Nov 2026 Details →
  8. 8 Pricing page github.com Checked 6 Nov 2026 Details →
  9. 9 Security / trust page github.com Checked 6 Nov 2026 Details →
  10. 10 Public status page www.githubstatus.com Checked 6 Nov 2026 Details →
  11. 11 Terms of service docs.github.com Checked 6 Nov 2026 Details →
  12. 12 Privacy policy docs.github.com Checked 6 Nov 2026 Details →
  13. 13 Subprocessor list docs.github.com Checked 6 Nov 2026 Details →
  14. 14 Code analysis (SAST & code quality) — found from sitemap github.com Checked 6 Nov 2026 Details →
  15. 15 Dependencies (SCA), licences & secrets — found from sitemap github.com Checked 6 Nov 2026 Details →
  16. 16 Developer workflow, quality gates & fixes — found from sitemap github.com Checked 6 Nov 2026 Details →
  17. 17 Platforms, deployment & administration — found from sitemap github.com Checked 6 Nov 2026 Details →
  18. 18 Platforms, deployment & administration — found from sitemap help.github.com Checked 6 Nov 2026 Details →
  19. 19 Source-code handling, security & compliance — found from sitemap github.com Checked 6 Nov 2026 Details →
  20. 20 Source-code handling, security & compliance — found from sitemap github.com Checked 6 Nov 2026 Details →