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 panel's verdict

GitHub Advanced Security adds CodeQL code scanning, Dependabot dependency alerts and secret scanning to the GitHub platform. Integration and administration leads at 7 to 8 — a documented REST API, webhooks, SARIF interoperability, SAML single sign-on, SCIM provisioning and a self-hosted Enterprise Server tier. Dependencies and secrets follows at 6 to 7, with secret scanning of the entire git history on all branches, validity checks, push protection and a 150+ provider partner programme documented end to end. Code analysis is the weakest criterion, scores clustering at 4: the captured pages publish no rule catalogue, no OWASP or CWE mapping, nothing on false-positive handling. The widest spreads are in pricing transparency and developer workflow, both 5 to 7 — unit prices ("$ 30 USD per active committer/month" for Code Security, "$ 19 USD" for Secret Protection) sit against an unexplained "active committer" count and unpriced Actions minutes, while merge-blocking rulesets are weighed against the absence of IDE-plugin and suppression documentation. Sovereignty scores 5 to 6: contracting runs with GitHub, Inc. under California law, with EU residency an Enterprise Cloud option, not the default.

Report an error

Speaks for it

  • Secret scanning covers the entire git history on all branches, with validity checks that contact the issuing service and push protection with delegated bypass
  • A documented REST API, webhooks and SARIF interoperability carry code-scanning results to third-party tools and external CI systems
  • Code Security and Secret Protection carry public prices of "$ 30 USD per active committer/month" and "$ 19 USD per active committer/month", with a 30-day trial
  • SOC 1 and SOC 2 Type II reports are produced annually, alongside FedRAMP Tailored, a published Data Protection Agreement, EU standard contractual clauses and Data Privacy Framework certification
  • Rulesets stop merges that add high-severity alerts, and alerts close automatically once the triggering code is fixed

Report an error

Held against it

  • Code analysis scored 4 across the bench, and the captured pages publish no rule catalogue, OWASP or CWE mapping, or false-positive handling
  • How an "active committer" is counted — the unit both add-on prices bill on — is not published on the captured pages
  • Code scanning consumes GitHub Actions minutes, whose cost the captured pages do not quantify
  • The terms license repository content for AI training unless you opt out in account settings or your use is governed by a customer or volume licensing agreement
  • Personal data is by default stored in a variety of locations including the United States, under a contract with GitHub, Inc. governed by US federal and California law

Report an error

Best for

  • Your repositories already live on GitHub and you want code, dependency and secret alerts inside the pull-request workflow
  • You need deep secret detection at scale — full git history, validity checks, push protection, and revocation through 150+ partner providers
  • You administer multiple organizations and want SAML single sign-on, SCIM provisioning and an audit log API from one enterprise account
  • You want to evaluate on public unit prices with a 30-day trial before purchase

Report an error

Avoid if

  • Your data protection officer requires a European processing chain by default — EU residency is a purchasable Enterprise Cloud option, and the AI-inference subprocessors OpenAI, Anthropic and xAI process in the United States
  • Your code sits on a host other than GitHub — the captured pages address other code hosts only through an Azure DevOps FAQ
  • You must compute a complete annual cost before signing — ask the vendor: the public pages we read do not show it
  • Your primary languages fall outside JavaScript, TypeScript, Java and Python — the only languages named on the captured pages are those four, for Autofix

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Code analysis (SAST & code quality)

Show reasoning
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 Lead Developer

CodeQL is described as industry-leading semantic analysis that finds vulnerabilities and coding errors, with alerts that close once the code is fixed and Copilot Autofix covering 90% of alert types in JavaScript, TypeScript, Java and Python. But the captured pages publish no rule list mapped to OWASP or CWE, no complexity, duplication or coverage measures, and nothing on false-positive handling — and PHP, the language most of our Laravel client work lives in, is not mentioned anywhere. 5 8 2 14

Report an error

The Application Security Engineer

CodeQL is described as semantic code analysis that finds vulnerabilities and coding errors, with multi-repository variant analysis and a public-preview scan for AI-application risks, so this is genuine SAST rather than a linter. The captured pages do not list languages and frameworks, publish no rule set mapped to OWASP or CWE, and give no information on taint analysis, a customer-writable rule language, quality metrics or false-positive handling — the depth I would need to justify it to my teams. 2 5 8 14

Report an error

The Engineering Manager

Code scanning with CodeQL's "industry-leading semantic code analysis" for vulnerabilities and coding errors is confirmed, with multi-repository variant analysis and a public preview that reviews pull requests for AI-application risks. But the captured pages give no information on which languages are supported at what depth, a published rule catalogue mapped to OWASP or CWE, custom rules, or the complexity, duplication, maintainability and technical-debt measures I would need to show per-team code health and hotspots. 2 5 8 14

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

The Product Security Officer

Code scanning is documented as semantic analysis of the repository for security vulnerabilities and coding errors, backed by CodeQL, multi-repository variant analysis, scheduled and event-triggered scans, and ingestion of third-party tools via SARIF. The captured pages leave the supported languages, the published rule set, quality and complexity metrics, and false-positive handling undescribed — precisely what I would need to file with an auditor. 5 8 2 14

Report an error

The Skeptic

Code scanning is documented as semantic analysis that finds "security vulnerabilities and coding errors", with Copilot Autofix claiming fixes for "90% of alert types" in four languages and multi-repository variant analysis on top. But the captured pages stop there: we found no public information on supported languages beyond those four, the rule catalog or its mapping to OWASP and CWE, custom rules, duplication and complexity metrics, or how false positives are measured and kept down. 2 5 8

Report an error

Dependencies (SCA), licences & secrets

Show reasoning
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 Lead Developer

This is the strongest area: reachability analysis in public preview, secrets validated against the issuing service and scanned across the entire git history on all branches, push protection with delegated bypass, custom and generic patterns, a 150+ provider partner program for revocation, plus Dependabot update pull requests and SBOM export. What the pages never show is licence detection and policies, malicious-package detection, or the vulnerability database and its sources. 6 15 8 3

Report an error

The Application Security Engineer

Secret scanning covers the entire Git history on all branches, validity checks contact the issuing service to see whether a credential is revoked, and push protection blocks secrets before they land with delegated bypass, custom and AI-generated patterns and scans of issues, pull requests, Discussions, wikis and gists — exactly my requirements. Dependabot adds grouped update pull requests, triage rules and reachability analysis in public preview with SBOM export. We found no public information on licence detection and policies, malicious-package detection, end-of-life components, container image scanning, or the vulnerability database and its sources. 3 6 8 15

Report an error

The Engineering Manager

Dependabot brings vulnerability alerts, grouped upgrade pull requests, reachability analysis in public preview and SBOM export, and the secrets side is genuinely deep — the entire Git history plus issues, discussions, wikis and gists are scanned, with validity checks, custom and generic patterns, a 150-plus-provider partner programme and push protection. We found no public information on the captured pages about licence detection and policies, the ecosystems and lockfiles covered, malicious-package and end-of-life detection, or the vulnerability database and how fast it is updated. 3 6 8 15

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

The Product Security Officer

Dependabot issues automated grouped vulnerability-fix pull requests with prioritisation by exploitation likelihood and reachability analysis in public preview, and each repository can export a software bill of materials — the artifact my Cyber Resilience Act file turns on — though the export format is not named and we found no public information on licence detection, malicious-package detection, end-of-life components or container scanning. Secret detection is the strongest part: the entire git history on all branches, validity checks that contact the issuing service, push protection before a secret lands, scans of issues, discussions, wikis and gists, and a 150-partner revocation programme. 8 15 6 3

Report an error

The Skeptic

The secrets side is documented end to end — the entire git history on all branches, plus issues, pull requests, Discussions, wikis and gists, validity checks that contact the issuing service, push protection with delegated bypass, and a 150+ provider partner programme that triggers revocation. Dependabot brings alert prioritisation with "reachability analysis (public preview)", grouped update pull requests and SBOM export, but we found no public information on which ecosystems are covered, licence detection and policies, malicious-package detection, or the vulnerability database and its sources. 3 6 8 15

Report an error

Developer workflow, quality gates & fixes

Show reasoning
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 Lead Developer

Rulesets that stop merges adding high-severity alerts, scans triggered on push, alerts tracked in issues that auto-close on fix, and Copilot Autofix are exactly the in-PR workflow I want for my teams. But I found no public information on IDE plugins running the same rules as the server — I need VS Code and PhpStorm parity — nor on ignoring findings or marking false positives for code alerts, and scan times are not documented. 2 5 8 15 20

Report an error

The Application Security Engineer

Alerts sit in the repository and close automatically when fixed, default setup applies one configuration to every repository and rulesets stop merges that add high-severity alerts, and Copilot Autofix is stated to fix 90% of alert types in JavaScript, TypeScript, Java and Python, with published remediation metrics. Scans run on schedule or on push, third-party tools can run in Actions or external CI, and alerts can be tracked with issues. The captured pages do not describe IDE plugins, a new-code baseline, deduplication, suppression with reasons, or typical scan times. 2 5 8 15 16

Report an error

The Engineering Manager

The gate story is real: rulesets stop merges that add high-severity alerts, alerts auto-close when the code is fixed, scans run on push or schedule through GitHub Actions, and Copilot Autofix claims automatic fixes for 90% of alert types in JavaScript, TypeScript, Java and Python — Java coverage matters to my teams. The documented path is GitHub-native only; we found no public information on IDE plugins matching server rules, triage and suppression with reasons, a new-code baseline, or typical scan times. 2 5 8 20

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

The Product Security Officer

Organisation-wide security configuration with rulesets that stop merges adding high-severity alerts is documented, push protection blocks secrets before they reach the code with delegated bypass, alerts auto-close on fix and can be tracked as issues, and Copilot Autofix with the model stated generates fixes for 90% of alert types in JavaScript, TypeScript, Java and Python. We found no public information on IDE plugins mirroring the server rules, a new-code baseline, suppression and triage rules, or typical scan times. 2 3 8 5

Report an error

The Skeptic

Scans run on push or schedule, rulesets "stop merges that add high-severity alerts", alerts close automatically once fixed and can be tracked as issues, Copilot Autofix proposes fixes, and push protection blocks secrets before they land. We found no public information on a new-code baseline, IDE plugins, ignoring findings or marking them as false positives, typical scan times, or the model behind autofix. 2 5 8

Report an error

Platforms, deployment & administration

Show reasoning
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 Lead Developer

A self-hosted Enterprise Server edition, SAML single sign-on with SCIM provisioning, an audit log API, an enterprise account managing multiple organizations, SARIF interop and webhooks plus a REST API for code scanning results are all documented. Since several of my clients sit on GitLab, I note that other code hosts appear only as an Azure DevOps FAQ question, and the captures show nothing on Jira integration or portfolio trend reports across repositories. 8 5 6 7 17 20

Report an error

The Application Security Engineer

Being native to GitHub, it offers a REST API and webhooks for code scanning alerts, SARIF interoperability with third-party tools, SAML single sign-on, SCIM provisioning, Enterprise Managed Users, an audit log API and an enterprise account managing multiple organizations, with GitHub Enterprise Server as a self-hosted plan and a public status page giving per-region, per-component uptime. An FAQ addresses use with Azure DevOps. We found no public information on Jira integration, granular per-team roles, or portfolio dashboards with trends. 1 5 7 8 10 17

Report an error

The Engineering Manager

Administration is strong at the enterprise level: SAML single sign-on, SCIM provisioning, Enterprise Managed Users, an audit log API, an enterprise account managing multiple organisations, webhooks plus a documented REST API for code-scanning alerts, and SARIF interoperability with third-party analysers; an Enterprise Server edition appears in the plan and licensing pages. For my specific wants the captured pages give no information on Jira routing of findings, granular roles per team, or portfolio dashboards with trends across repositories. 5 7 8 17

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

The Product Security Officer

Enterprise Cloud documents SCIM provisioning, SAML single sign-on, an audit log API, an Enterprise Account managing multiple organisations and regional deployments, and a self-hosted edition (Enterprise Server) is offered alongside a documented REST API, webhooks and SARIF interoperability. We found no public information on granular per-team roles, portfolio trend dashboards or code hosts beyond GitHub, apart from a FAQ addressing Azure DevOps. 8 5 10 11

Report an error

The Skeptic

There is a documented REST API and webhooks for code-scanning results, SARIF import and export, SAML single sign-on, SCIM provisioning, Enterprise Managed Users, an Audit Log API, enterprise accounts managing multiple organisations, and per-region status pages with 90-day uptime history. 1 5 7 8 10

Report an error

Source-code handling, security & compliance

Show reasoning
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 Lead Developer

A solid audit story: SOC 1 and SOC 2 type 2 reported annually, FedRAMP Tailored ATO, a published data protection agreement, EU standard contractual clauses, Data Privacy Framework certification, private repositories treated as confidential, 90-day deletion and export windows after termination, and an AI-training opt-out in account settings. Gaps: the pages state no encryption in transit or at rest, no compliance reports mapped to OWASP, CWE or PCI DSS, and no availability SLA — only support response times and the public status page. 8 11 12 10 13

Report an error

The Application Security Engineer

Annual SOC 1 and SOC 2 type 2 reports, a FedRAMP Tailored Authority to Operate and ISO are stated, a data protection agreement with EU standard contractual clauses is published, repository content is deleted within 90 days of cancellation, and the terms state plainly that content may train AI models with an opt-out, the AI inference subprocessors being named. A public status page gives component-level uptime. The captured pages say nothing about encryption in transit and at rest, or reports mapped to OWASP, CWE, PCI DSS or the EU Cyber Resilience Act, which is what my auditors ask for first. 8 10 11 12 13

Report an error

The Engineering Manager

Private repository contents are contractually confidential, AI training on customer content is licensed but with an account-settings opt-out and no sharing with third-party model providers, SOC 1 and SOC 2 Type II reports come annually alongside FedRAMP Tailored, a published data processing agreement and EU standard contractual clauses, and a public status page shows per-component 90-day uptimes. We found no public information on the captured pages about code retention periods, encryption in transit and at rest, a published availability SLA, or findings reports mapped to OWASP, CWE, PCI DSS or the Cyber Resilience Act. 8 9 10 11 12

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

The Product Security Officer

Retention is in writing — private repository content is confidential and remains mine, is deleted within 90 days of termination with a 90-day export window — and the AI position is explicit: content trains GitHub and its affiliates' models by default, with an opt-out in account settings or under a customer agreement, and no sharing with third-party model providers. SOC 1 and SOC 2 Type II annually and ISO are stated and a per-component public status page exists; we found no public information on encryption in transit and at rest, certification scope, an availability SLA, or findings mapped to OWASP, CWE, PCI DSS or the Cyber Resilience Act. 11 12 8 9

Report an error

The Skeptic

The terms grant GitHub and affiliates a licence to use your content "including by training AI Features" unless you opt out in settings or sit under an enterprise agreement, and Beta Previews "are not subject to the same security measures and auditing" — my kind of fine print. On the other side: SOC 2 Type II reports annually, FedRAMP Tailored ATO, a published Data Protection Agreement with standard contractual clauses and Data Privacy Framework certification, stated confidentiality for private repositories, 90-day deletion and export windows, and a status page with real per-component uptime. We found no public information on encryption in transit and at rest, a service-level availability commitment, or compliance reporting mapped to OWASP, CWE, PCI DSS or the Cyber Resilience Act. 8 9 10 11 12

Report an error

European sovereignty panel opinion

Show reasoning
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 Lead Developer

The subprocessor list is published with corporate and processing locations for every entry — AWS, Azure, GCP, OpenAI, Anthropic, xAI, Cerebras, nearly all in the United States — alongside a data protection agreement, contractual clauses and DPF certification, and Enterprise Cloud offers an EU data residency option on Azure. But the contract runs with GitHub, Inc. under California law, default storage includes the United States, and the AI inference chain is entirely American, so a German client with strict residency demands gets sovereignty only as a purchasable option. 12 13 8 11

Report an error

The Application Security Engineer

Enterprise Cloud offers an EU data-residency region on Microsoft Azure, GitHub B.V. in Amsterdam is named as a data controller, and a published subprocessor list names every provider with its processing locations, alongside a data protection agreement, EU standard contractual clauses and Data Privacy Framework certification. But by default data is stored in a variety of locations including the United States, personal data is shared with Microsoft as an affiliate, the terms are governed by California law, and every AI inference subprocessor listed is US-based. 8 11 12 13

Report an error

The Engineering Manager

There is an EU data-residency option on named Microsoft Azure infrastructure, GitHub B.V. in Amsterdam acts as a data controller, and a published subprocessor list gives names and processing locations with 30 days' advance notice of changes. Against that, the contract runs with GitHub, Inc. under US federal and California law, personal data is by default stored in a variety of locations including the United States, and the AI-inference and support subprocessors — OpenAI, Anthropic, xAI, Zendesk and others — are almost all US-based, so the chain is only as European as the paid residency option you buy. 8 11 12 13

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

The Product Security Officer

Contracting runs through GitHub, Inc. of San Francisco under Californian law and by default data is stored in a variety of locations including the United States, though Enterprise Cloud offers an EU data-residency deployment on Microsoft Azure and GitHub B.V. in Amsterdam acts as data controller. The subprocessor list is published with names, purposes and processing locations, showing the AI inference chain — OpenAI, Anthropic, xAI, AWS — processing in the United States; a data processing agreement and EU standard contractual clauses are published, and a self-hosted edition exists for running on our own servers. 12 13 8 11

Report an error

The Skeptic

The contracting entity is GitHub, Inc. of San Francisco under California law, default storage runs across "a variety of locations, including... the United States", and the AI-inference and support subprocessors — OpenAI, Anthropic, xAI, Zendesk — are almost all US-based. Credit where due: the subprocessor list with purposes and processing locations, the Data Protection Agreement, the contractual clauses and the Data Privacy Framework are published, GitHub B.V. of Amsterdam acts as data controller, and Enterprise Cloud offers an EU data-residency region on Microsoft Azure. That buys transparency rather than a European chain: EU residency is an enterprise option, not the default arrangement. 8 11 12 13

Report an error

Pricing transparency

Show reasoning
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 Lead Developer

The two security add-ons carry public prices — $30 USD per active committer per month for Code Security and $19 USD per active committer per month for Secret Protection — on top of plan prices of $4 USD and $21 USD per user per month, with free scanning on public repositories and most supply-chain features free. What I cannot compute from these pages: how an active committer is counted, the price of the self-hosted Server edition, annual-versus-monthly terms and VAT, and how many Actions minutes each scan burns on private repositories — which is exactly the metering that makes my bill jump. 8 20 5 15

Report an error

The Application Security Engineer

The security products carry public unit prices — $ 30 USD per active committer/month for Code Security and $ 19 USD per active committer/month for Secret Protection — on top of public platform plans ($ 0 USD Free, $ 4 USD per user / month Team, $ 21 USD per user / month Enterprise) with stated CI-minute allowances, free secret scanning on public repositories, a free risk assessment and a 30-day trial. How an active committer is counted is not explained, the Enterprise Server edition and premium support carry no price on the captured pages, and monthly versus annual terms and VAT treatment are not stated. 5 6 8 15 20

Report an error

The Engineering Manager

The add-on prices a buyer needs are public and per-scanner: "GitHub Code Security" at "$ 30 USD per active committer/month" and "GitHub Secret Protection" at "$ 19 USD per active committer/month", on top of published platform tiers, a free tier with Dependabot included, and a 30-day trial covering Enterprise, Copilot and Advanced Security. What is missing for a full annual computation: how an active committer is counted, annual versus monthly terms, VAT treatment, the price of the self-hosted Enterprise Server licence, and the cost of Actions minutes beyond the monthly allowance that code scanning consumes. 5 8 15 20

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

The Product Security Officer

Both security add-ons are priced publicly — Code Security at "$ 30 USD per active committer/month" and Secret Protection at "$ 19 USD per active committer/month" — on platform plans of $0, "$ 4 USD per user / month" and "$ 21 USD per user / month", with a 30-day trial and free risk assessments. We found no price for the self-hosted Enterprise Server edition, no definition of how an active committer is counted, no per-minute rate for the Actions minutes that code scanning consumes, and no VAT or annual-term treatment. 8 20 5 6

Report an error

The Skeptic

The headline numbers are public: "$4 USD" Team and "$21 USD" Enterprise per user per month, Code Security at "$30 USD per active committer/month", Secret Protection at "$19 USD per active committer/month", most supply-chain features free, a 30-day trial, price locked for the term and 30 days' notice of increases. But we found no public information on how an "active committer" is counted — the exact number the bill turns on — nor on VAT treatment, annual terms, Enterprise Server pricing, or repository and scan limits; code scanning also consumes GitHub Actions minutes, whose cost the captured pages do not quantify. 5 8 11 15 20

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 →