# GitGuardian — Code Security & Quality (SAST/SCA)

GitGuardian by GitGuardian SAS holds a panel rating of 3/5 from 6 AI judges (category median 3/5), as of 2026-11-06. Provenance: EU-Made; sovereignty: 3 of 6 dimensions proven.

- Vendor: GitGuardian SAS (https://www.gitguardian.com)
- Category: [Code Security & Quality (SAST/SCA)](https://whats-best.ai/software/code-security.md)
- Provenance (editorial classification): EU-Made
- Canonical page: https://whats-best.ai/software/code-security/gitguardian
- Alternatives: https://whats-best.ai/software/code-security/gitguardian/alternatives ([markdown](https://whats-best.ai/software/code-security/gitguardian/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-06 · oldest source captured 2026-11-06

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: GitGuardian SAS
- Headquarters: Incorporated in France [S14]
- Data hosting: Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan: Yes, per the vendor’s own page [S1]

## The panel's verdict

Judged on its own pages, GitGuardian is a secrets-detection platform rather than a broad code analyser. Code analysis scored a flat 0: the pages brand "a native SAST for GitHub" but document only hardcoded-credential detection, with no public information on data-flow or taint analysis or OWASP/CWE rule sets. The strengths sit elsewhere. Sovereignty scored a flat 8: the contracting entity is GitGuardian SAS of Paris, EU customers are hosted on AWS eu-central-1 in Frankfurt, a Data Processing Addendum and a subprocessors page are published, and a self-hosted edition keeps code and findings on your own infrastructure — though subprocessor locations are not shown on the captured pages and no migration from the US platform is supported. Integration and administration scored 7-8 and dependencies and secrets 6-8: 550+ specific detectors, a published 91% true-positive rate and merge-blocking status checks, against no public information on dependency analysis or SBOM export. Pricing transparency sits at 4 — free Starter limits published, Growth contact sales. No criterion registered a genuine disagreement; the widest spread, 6 to 8, is on dependencies and secrets.

**Speaks for it:**
- Secrets detection documented in depth: 550+ specific detectors plus generic high-entropy patterns, full-history scans across all branches, and a published 91% true-positive rate.
- Leak prevention built into the workflow, with pre-commit, pre-push and pre-receive hooks plus required status checks that block merges.
- A self-hosted edition on Helm or KOTS keeps code and findings on your own infrastructure.
- Data handling stated concretely: only patches with detected secrets are collected, and all customer data is removed at the end of the relationship.
- SOC 2 Type II maintained since 2022 with annual independent audits by Prescient Assurance.

**Held against it:**
- Code analysis scored 0: we found no public information on taint or data-flow analysis, OWASP or CWE rule sets, or complexity and duplication metrics.
- We found no public information on dependency vulnerability analysis, licence policies or SBOM export.
- We found no published service-level agreement, and no public statement on whether customer code trains AI models or which provider runs the AI risk scoring.
- We found no public information on SARIF or CSV export of findings.
- Above the free Starter plan, the Growth and Enterprise tiers are contact sales with no public per-developer price.

**Best for:**
- Your primary exposure is leaked credentials in code, git history and collaboration tools such as Slack, Jira and Confluence.
- You want secrets scanning enforced inside existing CI on GitHub, GitLab, Bitbucket or Azure DevOps, including self-managed variants such as GitHub Enterprise and Bitbucket Data Center.
- You must keep code and findings on your own infrastructure and can run the self-hosted edition on your own Kubernetes.
- You are an EU buyer who wants the EU region on AWS eu-central-1 in Frankfurt and a French contracting entity, with Standard Contractual Clauses covering US transfers.

**Avoid if:**
- You need taint or data-flow analysis, OWASP/CWE-mapped vulnerability rules or code-quality metrics — code analysis scored 0 and the bench judged the product a secrets detector.
- You need dependency composition, licence policies or SBOM export from the same platform — the judges' conclusion is that supply-chain composition would still need a second tool.
- You must compute an annual cost from public pages — above the free Starter plan the tiers are contact sales.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Lead Developer | The Application Security Engineer | The Engineering Manager | The Platform Engineer | The Product Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Code analysis (SAST & code quality) | 0/5 | 0/5 | 0/5 | 0/5 | 0/5 | 0/5 |
| Dependencies (SCA), licences & secrets | 3/5 | 3/5 | 4/5 | 3.5/5 | 3/5 | 3/5 |
| Developer workflow, quality gates & fixes | 3/5 | 3/5 | 3/5 | 3.5/5 | 3.5/5 | 3/5 |
| Platforms, deployment & administration | 3.5/5 | 3.5/5 | 4/5 | 4/5 | 4/5 | 4/5 |
| Source-code handling, security & compliance | 3.5/5 | 3.5/5 | 3.5/5 | 4/5 | 3.5/5 | 3.5/5 |
| European sovereignty | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **3/5** | **3.5/5** | **3/5** | **3/5** |

### The judges

- **The Lead Developer** (v1.0): Lead developer at a web agency in Cologne with fourteen developers building Laravel, TypeScript and React Native projects for clients on GitHub and GitLab. Wants every merge request checked for bugs, injection flaws and vulnerable packages before review, comments in the merge request rather than a separate dashboard, the same rules in VS Code and PhpStorm, few false positives, and a bill that does not jump each time a freelancer pushes a commit.
- **The Application Security Engineer** (v1.0): Application security engineer at a payments company in Frankfurt with 120 developers, two of them security champions per team, under PCI DSS and DORA. Wants taint analysis that follows user input across files, reachability so the backlog holds only vulnerable code that is actually called, secrets checked for validity across the whole git history, push protection, custom rules for in-house frameworks, and reports an auditor accepts.
- **The Engineering Manager** (v1.0): Head of engineering at a B2B SaaS company in Munich with six teams and a ten-year-old Java and Kotlin codebase. Wants technical debt and code health shown per team and hotspot, a quality gate on new code that every team keeps, trends to show the board that the rewrite budget worked, findings routed to Jira, single sign-on and roles per team, and to know what the AI-written code the teams now merge does to the numbers.
- **The Platform Engineer** (v1.0): 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.
- **The Product Security Officer** (v1.0): Product security officer at a machine builder in Baden-Württemberg whose controllers and service apps fall under the EU Cyber Resilience Act. Needs an SBOM per release in a standard format, every component's vulnerabilities and licences tracked after shipping, evidence of secure development an auditor can file, and to know where the firmware source code is stored, for how long, and whether any AI model is trained on it.
- **The Skeptic** (v1.0): Has seen "zero false positives" bury a team under four thousand findings on day one, a "free for open source" plan that counted every bot as a contributor, and an "AI autofix" that shipped the repository to a model in the US. Asks how contributors are counted, which languages get real data-flow analysis rather than regular expressions, what happens to the code after a scan, whether the findings export when the contract ends — and what the second year costs.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 3 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in FR | 2/2 | [S14] |
| Hosting location | Not determined | — | — |
| Hosting options | Self-hostable | 1/1 | [S8] |
| Open source | Not determined | — | — |
| Data processing agreement | Published, self-serve | 1/1 | [S12] |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Audit frequency: annual [S24]
- Audit logs: yes [S4]
- Auditor: Prescient Assurance [S24]
- Background checks: all contractors and employees · yes [S24]
- CCPA rights: yes [S14]
- Frameworks: PCI DSS · CIS · NIS2 · SOC 2 · DORA · ISO 27001 · SOX · GDPR [S1]
- GDPR: yes [S3]
- International transfer scc: Standard Contractual Clauses (Art. 46 GDPR) · yes [S14]
- Saas EU GDPR: EU · yes [S23]
- SOC 2: 2022 · SOC 2 Type II · yes [S24]

**Data**
- Account deactivation via email: support@gitguardian.com · yes [S14]
- Commit collection policy: only commits with detected secrets · yes [S23]
- Deletion at end of service: end of service relationship · yes [S24]
- Historical scan metrics: number of commits scanned · number of branches scanned [S23]
- Historical scan scope: all commits across all branches · patches containing secrets only [S23]
- Log retention: 365 [S24]
- No sensitive personal data: no [S14]
- Perimeter source metadata: name · size_bytes · visibility · vcs_unique_identifier · stars · forks · watchers [S23]
- Retention commercial data: commercial data · 2 [S14]
- Retention contact data: request/contact data · 2 [S14]
- Retention max general: some data, maximum unless longer required · 10 [S14]
- Retention rights requests: data subject rights requests · 5 [S14]
- Vcs members access: read-access to VCS members · compute number of seats for billing [S23]

**Hosting**
- Aws: AWS [S24]
- EU migration not supported: no [S23]
- EU region: eu-central-1 / Frankfurt · 5 · 100 [S10]
- Saas regions: Frankfurt, Germany · East Coast of the USA [S3]
- Self hosted: bare metal · private or public clouds · existing Kubernetes cluster · yes [S3]
- Self hosted base URL: https://api.gitguardian.com/ · https://dashboard.gitguardian.mycorp.local/exposed/ · yes [S21]
- Self hosted options: Helm · KOTS [S8]
- Self hosting: yes [S7]
- US region: us-west-2 / Oregon · 5 · 99.95 [S10]

**Integrations**
- Action name: GitGuardian/ggshield/actions/secret@v1.56.1 [S20]
- Action repository path: Actions found in actions directory of GitHub repository [S20]
- Alerting destinations: Get alerted of new incidents on third-party applications [S6]
- API available: yes [S11]
- Bring your own source: yes [S6]
- Categories: alerting · ci/cd · docker · version control system · siem or itsm [S16]
- Cicd pipeline: yes [S15]
- Cicd slack jira containers: CI/CD pipelines · infrastructure-as-code files · Slack · Jira · container images [S2]
- Cicd sources: ggshield · Secrets detection in CI/CD workflows via ggshield CLI [S6]
- Code repositories: Scan code repositories to detect incidents in real-time and in history [S6]
- Container registries: Scan docker images to detect secret incidents [S6]
- Docker scanning: ggshield · Scan docker images for secrets via ggshield CLI [S6]
- Documentation sources: Scan documents to detect secret incidents in real-time [S6]
- Ecosystem: Integrations listed in product navigation [S11]
- Env variable: GITGUARDIAN_API_KEY environment variable [S20]
- File storage sources: Scan stored files to detect secret incidents [S6]
- Git hooks: ggshield · Secrets detection at git hook level via ggshield CLI [S6]
- Issue tracking destinations: Create tickets and link them to GitGuardian incidents [S6]
- Messaging sources: Scan messaging channels to detect secret incidents in real-time [S6]
- Native platforms: GitHub · GitLab · Bitbucket · Azure DevOps [S17]
- Nhi governance cicd: Monitor CI/CD pipelines for secrets leaks and insecure code [S6]
- Nhi governance iam: Detect exposed credentials and misconfigurations in identity systems [S6]
- Nhi governance infrastructure: Secure secrets and identities across infrastructure clusters [S6]
- Nhi governance vault: Secrets detection for non-human identities (NHIs) [S6]
- Page: Integrations directory offered [S1]
- Platforms: GitHub · GitLab · Bitbucket · Azure DevOps [S16]
- Public API: yes [S7]
- Rest API: REST API for programmatic incident handling [S4]
- Scm: GitHub · GitLab · Bitbucket · Azure DevOps · yes [S2]
- Sdlc categories: alerting · CI/CD · docker · version control system · SIEM or ITSM [S15]
- Sdlc categories: alerting · CI/CD · Docker · version control system · SIEM or ITSM [S17]
- Secrets manager sync: Synchronize secrets detection with your secrets manager [S6]
- Siems: yes [S4]
- Source control: GitHub · GitLab · Bitbucket · Azure Repos · historical scan · continuous monitoring [S5]
- Ticketing sources: Scan projects to detect secret incidents in real-time [S6]
- Total count: 67 [S6]
- Vcs: GitHub · GitLab · Bitbucket · Azure Repos [S7]

**Legal**
- Address: GitGuardian SAS, 54 rue de Seine, 75006 Paris, France [S13]
- Content license: Users grant GitGuardian a limited, revocable, non-transferable license to User Content; users remain owners [S13]
- Controller identity: GitGuardian SAS · 54 rue de Seine 75006 Paris, France · GitGuardian Inc., 185 Alewife Brook Parkway Ste 210 Cambridge MA 02138 [S14]
- Cookie policy: Cookie Policy [S12]
- Cookie policy URL: https://www.gitguardian.com/legal/cookie-policy [S14]
- Cookies: yes [S13]
- Dispute resolution: Mandatory informal dispute resolution via legal@gitguardian.com before formal claims; 60-day window [S13]
- Dmca email: legal@gitguardian.com [S13]
- Dmca repeat infringer: yes [S13]
- DPA: Data Processing Addendum [S12]
- Entity: GitGuardian SAS [S13]
- Governing law americas: New York law for Americas users; exclusive venue in federal or state courts in the State of New York [S13]
- Governing law other: French law and courts of Paris for users outside the Americas [S13]
- Last updated: 31/01/2024 [S13]
- Lead supervisory authority: CNIL (France) [S14]
- Legal notice: Legal Notice [S12]
- Liability cap: 100 [S13]
- License to user: Site license limited to personal, non-commercial use; revocable and non-transferable [S13]
- Minimum age: 13 [S13]
- No data sale: no [S14]
- Notice last updated: 2026-07-29 [S14]
- Policies: yes · Good Samaritan Developer Alerting Service · Public Security Policy · Speak Up Policy [S12]
- Privacy documents: yes · Privacy Policy · Global Applicant and Candidate Privacy Notice · Client, Partner and Prospect Privacy Notice [S12]
- Response time limit: 30 [S14]
- Terms documents: yes · Master Service Terms and Conditions · Website Terms of Use · GitGuardian Terms of Service [S12]
- Third party materials: Site may include third-party materials and links; GitGuardian disclaims responsibility for them [S13]
- User termination: yes [S13]
- Warranty disclaimer: yes [S13]

**Pricing**
- Free plan token fallback: personal access token [S20]
- Free tier: yes [S1]
- Free tier: yes [S3]
- Free tier: yes [S15]
- Free tier: yes [S16]
- Free tier: Free start for scanning GitHub code repos [S17]
- Free trial: Free trial, first repo in 5 minutes, no credit card [S1]
- Pricing page: Pricing page exists in navigation [S1]
- Service accounts plans: Growth · Enterprise [S20]
- Starter free tier: yes · 25 · 10000 · 500 [S8]

**Product**
- Access control: yes [S24]
- AI agents security: platform includes Secrets Security, NHI Governance and AI Agents security [S11]
- Alerting integrations: yes [S3]
- Analytics: Incident trend analytics for security posture assessment and per-developer improvement areas [S5]
- API examples languages: Code examples in all supported programming languages, e.g. Python and Go [S21]
- API key required: yes [S20]
- API reference: API Reference documentation exists for the GitGuardian API [S21]
- API scan route: API includes a scan route [S21]
- Asset inventory: yes [S24]
- Audit logs: yes [S3]
- Automatic scan: yes [S16]
- Backups: yes · 14 · yes [S24]
- Breach intel reports: Site publishes documented secret breaches feed [S1]
- Bug bounty: private · yes [S24]
- Bug bounty platform: yes · YesWeHack [S24]
- Business continuity: yes [S24]
- Change management: yes [S24]
- Chatops channels: yes [S3]
- Ci cd pipeline: yes [S16]
- Ci cd scanning: yes [S3]
- Ci detection: GitGuardian can detect secrets in CI pipelines via ggshield CI integrations [S19]
- Ci incidents dashboard: CI-detected incidents are also raised in the GitGuardian dashboard [S19]
- Ci integrations list: Jenkins CI · GitHub Actions · GitLab CI/CD · Azure pipelines · Bitbucket pipelines · Circle CI · Drone CI · Travis CI [S19]
- Cicd integration: yes [S17]
- Cli: CLI detects and prevents 450+ types of hardcoded secrets pre-push [S7]
- Cli ggshield: GitGuardian CLI (ggshield) · pre-commit · pre-push · IDE · AI coding tools · yes [S1]
- Cli ggshield: ggshield [S3]
- Cli tool: yes [S11]
- Collab tool leaks: Slack · Jira · Confluence [S2]
- Commits analyzed: secret scanning engine refined through analysis of over 4 billion commits [S2]
- Commits scanned: 2018 · 4000000000 [S15]
- Commits scanned: 2018 · 4 billion+ [S17]
- Custom detectors: yes [S2]
- Custom detectors: yes [S3]
- Custom detectors: yes [S15]
- Custom detectors: yes [S16]
- Custom detectors: yes [S17]

**Subprocessors**
- Ad analytics named: Google Ads · Google analytics · X · Facebook · Quora · Bing ads · Linkedin · Piwik · advertising and analytics [S14]
- List page: A Subprocessors page is published under Privacy [S12]
- List URL: https://www.gitguardian.com/legal/subprocessors [S24]
- Service providers: payment services · hosting services · authentication services · cybersecurity · anti-fraud services · advertising [S14]

**Support**
- Data subject requests contact: legal@gitguardian.com [S14]
- Docs and API: documentation · API · status page [S1]
- Documentation: yes [S11]
- Documentation API: yes [S17]
- Good samaritan: Good Samaritan Program exists [S1]
- Interactive tour: Interactive tour, 5 minutes, no signup [S1]
- Marketplace ranking: #1 Security App on GitHub Marketplace [S8]
- Security contact: security@gitguardian.com [S24]
- SSO issue assistance: support team available for SSO issues [S22]
- Status page: yes [S11]

168 more facts on the canonical page: https://whats-best.ai/software/code-security/gitguardian

## Questions

### 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](https://whats-best.ai/evidence/20754).

### 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](https://whats-best.ai/evidence/20331).

### What are the best alternatives to GitGuardian?

As of 19 Nov 2026, the panel rates [SonarQube (3.5/5)](https://whats-best.ai/software/code-security/sonarqube), [Aikido Security (3.5/5)](https://whats-best.ai/software/code-security/aikido) and [Endor Labs (3.5/5)](https://whats-best.ai/software/code-security/endor-labs) 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](https://whats-best.ai/software/code-security/sonarqube) (EU origin, foreign-owned, Switzerland). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [GitGuardian alternatives](https://whats-best.ai/software/code-security/gitguardian/alternatives).

## Head-to-head

- [GitGuardian vs GitHub Advanced Security](https://whats-best.ai/compare/gitguardian-vs-github-advanced-security.md)

## What this page leaves out

- 10 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 8 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 5 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown.
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement.

## Sources

- [S1] Vendor homepage: https://www.gitguardian.com/ (checked 2026-11-06)
- [S2] Features page (secrets scanning): https://www.gitguardian.com/secrets-scanning-tool (checked 2026-11-06)
- [S3] Features page (internal repositories): https://www.gitguardian.com/monitor-internal-repositories-for-secrets (checked 2026-11-06)
- [S4] Features page (public GitHub monitoring): https://www.gitguardian.com/monitor-public-github-for-secrets (checked 2026-11-06)
- [S5] Features page (code security): https://www.gitguardian.com/code-security (checked 2026-11-06)
- [S6] Integrations page: https://www.gitguardian.com/integrations (checked 2026-11-06)
- [S7] Documentation: https://docs.gitguardian.com/ (checked 2026-11-06)
- [S8] Pricing page: https://www.gitguardian.com/pricing (checked 2026-11-06)
- [S9] Trust centre: https://trust.gitguardian.com/ (checked 2026-11-06)
- [S10] Public status page: https://status.gitguardian.com/ (checked 2026-11-06)
- [S11] About page: https://www.gitguardian.com/about-us (checked 2026-11-06)
- [S12] Legal documents: https://www.gitguardian.com/legal (checked 2026-11-06)
- [S13] Terms of service: https://www.gitguardian.com/legal/terms-of-use (checked 2026-11-06)
- [S14] Privacy policy: https://www.gitguardian.com/legal/privacy-policy (checked 2026-11-06)
- [S15] Code analysis (SAST & code quality) — found from sitemap: https://www.gitguardian.com/solutions/sast-github (checked 2026-11-06)
- [S16] Code analysis (SAST & code quality) — found from sitemap: https://www.gitguardian.com/solutions/github-sast-scanning (checked 2026-11-06)
- [S17] Dependencies (SCA), licences & secrets — found from sitemap: https://www.gitguardian.com/solutions/git-secrets (checked 2026-11-06)
- [S18] Dependencies (SCA), licences & secrets — found from sitemap: https://docs.gitguardian.com/secrets-detection/home (checked 2026-11-06)
- [S19] Developer workflow, quality gates & fixes — found from sitemap: https://docs.gitguardian.com/internal-monitoring/prevent/detect-secrets-in-ci-cd-pipelines (checked 2026-11-06)
- [S20] Developer workflow, quality gates & fixes — found from sitemap: https://docs.gitguardian.com/ggshield-docs/integrations/cicd-integrations/github-actions (checked 2026-11-06)
- [S21] Platforms, deployment & administration — found from sitemap: https://docs.gitguardian.com/api-docs/api-reference (checked 2026-11-06)
- [S22] Platforms, deployment & administration — found from sitemap: https://docs.gitguardian.com/platform/enterprise-administration/saml-sso-configuration (checked 2026-11-06)
- [S23] Source-code handling, security & compliance — found from sitemap: https://docs.gitguardian.com/platform/security-data-privacy/data-retention (checked 2026-11-06)
- [S24] Source-code handling, security & compliance — found from sitemap: https://www.gitguardian.com/legal/public-security-policy (checked 2026-11-06)

---

Cite as: whats-best.ai, "GitGuardian — Code Security & Quality (SAST/SCA)", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/code-security/gitguardian

Corrections: https://whats-best.ai/correct/1649?target=page
