PAGES
← all tools
◆ Secrets Detection & Management

GitGuardian Detection Engine

changelog-20261031-214c3208 commercial

GitGuardian Detection Engine scans code repositories to identify and alert on exposed secrets, credentials, and sensitive data.

Summary

GitGuardian Detection Engine is a commercial secrets-detection engine that scans code, patches, and text like GitHub gists or Slack messages for exposed credentials, and it runs as a backend service rather than something you install locally. It combines specific detectors tuned to individual credential types, such as AWS keys or Azure service keys, with generic pattern-based detectors that catch what the specific ones miss, and it improves both through explicit and implicit feedback collected from the alerts it sends. This suits security and platform teams responsible for catching leaked credentials across an organization's repositories rather than individual developers scanning their own machines. It sits in the secrets-detection category, distinct from general static-analysis or SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment. tools, focused specifically on finding live credentials before or after they reach version control.

GitGuardian Detection Engine scans code repositories to identify and alert on exposed secrets, credentials, and sensitive data.

How GitGuardian Detection Engine helps

Which credentials in this patch or file are actual live secrets rather than test fixtures or placeholders?

runs specific detectors tuned to each credential type, like AWS keys or Azure service keys, alongside generic entropy and pattern detectors that catch what the specific ones miss, and returns a match per credential type found

Is this exposed value actually still valid, or already revoked?

validity checkers call out to the credential's own service, for example the Datadog, npm, or LiteLLM APIs, and report back whether the key currently authenticates

Which of the secrets flagged in this scan are false alarms I can safely ignore?

folds in explicit feedback from developers and security teams marking past alerts as false, and implicit feedback such as a repository being taken down minutes after an alert, to keep precision high on the detectors still running

Did a secret leak into a gist, Slack message, or text snippet rather than a source file?

takes any string as input, with the filename as an optional hint, so it can scan things that are not committed code, not just files in a repository

Which specific credential type or vendor format triggered this alert?

matches against a named detector for that provider, such as Azure Service Bus keys, TomTom API keys, or GitHub App tokens, so the alert identifies the exact kind of secret rather than a generic "high entropy string" flag

all 6 features, with the evidence for each →

Languages

Not documented

Features

6 capabilities

Built from GitGuardian Detection Engine's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • GitGuardian Detection Engine covers 1 of the 2 secrets and credential hygiene capabilities we track.

What GitGuardian Detection Engine offers you

All capabilities 6 capabilities
Secret and credential detection shipped Detects secrets, API keys, tokens, and credentials across a wide range of services and platforms in scanned content. 483 releases · 6 other sources · first seen Apr 2024

Shared capability: Secret scanning

release 483 total

  • The microsoft_azure_storage_account_key_with_account_name detector moves to its own detector group. changelog · Oct 2026 · source · release history
  • The jenkins_api_token detector now also matches the Jenkins instance URL. changelog · Oct 2026 · source · release history
  • Adds a new analyzer for Weights & Biases API keys, including a detector checker. Detection Engine Updates Version 2.175 (2026-10-27) · Oct 2026 · source · release history
  • Activates the Bitbucket Data Center HTTP access token checker (Bitbucket HTTP Access Token with Prefix), now available with a required custom host. Detection Engine Updates Version 2.175 (2026-10-27) · Oct 2026 · source · release history
  • Adds a new detector for Portainer API keys that can match the key alone or together with the URL of the Portainer instance.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ Detection Engine Updates Version 2.175 (2026-10-27) · Oct 2026 · source · release history
  • Activates the Jira Data Center personal access token checker, now available with a required custom host. Detection Engine Updates Version 2.175 (2026-10-27) · Oct 2026 · source · release history

docs

  • Broad coverage with 650+ detectors We have developed a library of specific and generic detectors. See the list of supported credentials docs update · Oct 2026 · source
  • September 28, 2026 This release adds new detectors for Ory API keys, Kong Konnect personal access tokens, AppSignal API keys, PostHog OAuth access and refresh tokens, Datadog service access tokens, NinzaSMS API keys, TypeSafe AI API keys, and Mistral AI's new prefixed API key format. changelog · Oct 2026 · source
  • September 14, 2026 This release ships ten new detectors, including Brightcove OAuth credentials, Infor ION API credentials, Telnyx API keys, Bifrost virtual keys, Jira Data Center personal access tokens, and a generic Sanctum token detector. changelog · Sep 2026 · source
  • August 31, 2026 This release brings improved n8n instance detection for the n8n API Key and n8n MCP Access Token detectors, along with better recall for Hashicorp Vault AppRole Authentication credentials. Three checkers were fixed: Scaleway Token, Workato API Key and Open VSX Access Token. changelog · Sep 2026 · source
  • August 17, 2026 This release ships six new detectors — Firebase ID tokens, Coze access tokens, Keycloak access tokens, Keycloak refresh and offline tokens, Fish Audio API keys, and Azure Custom Vision Training keys — along with a new analyzer for Apify tokens. changelog · Sep 2026 · source
  • Broad coverage with 600+ specific detectors We have developed the vastest library of specific detectors being able to detect 600+ different types of secrets (10 times more than the current competition). You can find the exhaustive list seen Aug 2026 · source
Detector precision and recall tuning shipped Refines existing detectors to reduce false positives and false negatives by improving pattern matching, validation logic, and domain filtering. 27 releases · first seen Sep 2025

release 27 total

  • The postgres_assignment_attached_port and postgres_assignment_no_port detectors have been merged into postgres_assignment. changelog · Oct 2026 · source · release history
  • The ftp_credentials_assignment detector now only captures FTP secrets, not SFTP — SFTP secrets require the new sftp_credentials_assignment detector. changelog · Oct 2026 · source · release history
  • The planetscale_database_password_with_host_and_username detector has been merged into planetscale_database_password. changelog · Oct 2026 · source · release history
  • The grafana_service_account_token_with_host detector has been merged into grafana_service_account_token. changelog · Oct 2026 · source · release history
  • The azure_event_grid_access_key_with_host detector has been merged into azure_event_grid_access_key. changelog · Oct 2026 · source · release history
  • The kubernetes_jwt_with_host detector has been merged into kubernetes_jwt. changelog · Oct 2026 · source · release history
Credential validity checking shipped Verifies whether detected credentials are active and valid by testing them against their respective service endpoints. 23 releases · first seen May 2024

release 23 total

  • Adds a checker for ODBC connection strings supporting SQL Server, MySQL, PostgreSQL, Oracle, and DB2 databases. Detection Engine Updates Version 2.175 (2026-10-27) · Oct 2026 · source · release history
  • Enables validity checker for SMTP credentials. changelog · Oct 2026 · source · release history
  • Merges the generic_database_assignment_attached_port detector into the generic_database_assignment detector. changelog · Sep 2026 · source · release history
  • Merges the generic_database_assignment_attached_port detector into the generic_database_assignment detector. Detection Engine Updates Version 2.172 (2026-09-14) · Sep 2026 · source · release history
  • Expands the Figma personal access token analyzer to report the folders:read scope, replacing the deprecated projects:read scope. Detection Engine Updates Version 2.172 (2026-09-14) · Sep 2026 · source · release history
  • New Relic Key, New Relic Insights Insert Key, and New Relic APM License Key checkers can now identify revoked keys via an empty POST request. Detection Engine Updates Version 2.170 (2026-08-17) · Aug 2026 · source · release history
Detector lifecycle management shipped Enables detectors and checkers to be disabled or removed when the underlying service is discontinued or no longer supported. 19 releases · first seen Nov 2025

release 19 total

  • The line_notify_token detector has been removed. changelog · Oct 2026 · source · release history
  • The planetscale_database_password_with_host_and_username detector is removed — merged into planetscale_database_password. Detection Engine Updates Version 2.174 (2026-10-13) · Oct 2026 · source · release history
  • The grafana_service_account_token_with_host detector is removed — merged into grafana_service_account_token. Detection Engine Updates Version 2.174 (2026-10-13) · Oct 2026 · source · release history
  • The line_notify_token detector and checker have been removed (the LINE Notify service is no longer available). Detection Engine Updates Version 2.174 (2026-10-13) · Oct 2026 · source · release history
  • The postgres_assignment_attached_port and postgres_assignment_no_port detectors are removed — merged into postgres_assignment. Detection Engine Updates Version 2.174 (2026-10-13) · Oct 2026 · source · release history
  • The kubernetes_jwt_with_host detector is removed — merged into kubernetes_jwt. Detection Engine Updates Version 2.174 (2026-10-13) · Oct 2026 · source · release history
Validity checker hardening shipped Strengthens validity checkers to reject false-valid results caused by intercepting proxies or unexpected response formats. 2 releases · first seen Aug 2026

release

  • Hardens the Azure Event Hub checker with the same Atom-feed validation requirement. changelog · Aug 2026 · source · release history
  • Azure Event Hub and Azure Service Bus checkers now only report a key as valid when the 200 response is a genuine Service Bus Atom feed, blocking false-valid results behind intercepting proxies. Detection Engine Updates Version 2.169 (2026-08-03) · Aug 2026 · source · release history
File type scanning coverage shipped Extends secret scanning to additional file formats, including HTML and Markdown files. 2 releases · first seen Jul 2026

Shared capability: Secret scanning

release

  • HTML and Markdown file scanning extended to npm, GitHub Personal Access, GitHub OAuth, GitHub App, and Slack Application tokens. Detection Engine Updates Version 2.168 (2026-07-20) · Jul 2026 · source · release history
  • Extends scanning scope to HTML and Markdown files for npm, GitHub (Personal Access, OAuth and App), and Slack Application Credentials tokens Detection Engine Updates Version 2.168 (2026-07-20) · Jul 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for GitGuardian Detection Engine, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail GitGuardian Detection Engine puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Commercials

pricing & packaging history · GitGuardian vendor page

42 readings of GitGuardian's pricing page since Sep 2021, with 10 relaunches of its plan lineup and 24 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.

Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.

See plans →

Website history

gitguardian.com, every change

GitGuardian's home page and 36 more pages as they looked each month from August 2021 to October 2026: 48 renders, 2 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Coverage

Missing something? Tell us

What GitGuardian Detection Engine connects to, runs on and detects, read from its release notes and docs. So far: 13 new detections, 13 updated detections.

Show
When

26 changes, tracked since Sep 28, 2026.

  • Oct 272026

    new Portainer API Key detector

    Version 2.175.0 adds a new detector for Portainer API keys, which can also match the URL of the Portainer instance.

    Detection Engine Updates Version 2.175 (2026-10-27) Source ↗

  • Oct 272026

    new Weights & Biases API Key checker and analyzer

    With ODBC Connection String, SQL Server, MySQL, PostgreSQL, Oracle, DB2

    It adds checkers for Weights & Biases API keys and for ODBC connection strings (SQL Server, MySQL, PostgreSQL, Oracle and DB2).

    Detection Engine Updates Version 2.175 (2026-10-27) Source ↗

  • Oct 272026

    new Custom-host checkers activated for eight services

    With JFrog Artifactory tokens, AWS Cognito OAuth 2.0 credentials, Bitbucket Data Center HTTP access tokens, Jira Data Center personal access tokens, Microsoft Azure Storage account keys, Okta keys

    Eight checkers that need a custom host are now available: JFrog Artifactory tokens and reference tokens, AWS Cognito OAuth 2.0 credentials, Bitbucket Data Center HTTP access tokens, Jira Data Center personal access tokens, Microsoft Azure Storage account keys, and Okta keys and tokens.

    Detection Engine Updates Version 2.175 (2026-10-27) Source ↗

  • Oct 272026

    updated json_web_token recall improvement

    Recall improves for json_web_token , which now finds tokens split across several string literals

    Detection Engine Updates Version 2.175 (2026-10-27) Source ↗

  • Oct 272026

    updated sentry_org_auth_token recall improvement

    and for sentry_org_auth_token .

    Detection Engine Updates Version 2.175 (2026-10-27) Source ↗

  • Oct 272026

    updated jenkins_api_token host URL matching

    jenkins_api_token can now also match the Jenkins instance URL.

    Detection Engine Updates Version 2.175 (2026-10-27) Source ↗

Changes per month New Updated Retired
2026-0915
2026-1011
How we count

Read from 3 of 64 release notes and docs updates we hold for GitGuardian Detection Engine. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through GitGuardian Detection Engine's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

64 entries

  1. October 20266
  2. September 20267
  3. August 20265
  4. July 20264
  5. June 20263
  6. May 20262
  7. April 20262
  8. March 20263
  9. February 20261
  10. January 20262
  11. December 20252
  12. November 20252
  13. October 20252
  14. September 20252
  15. August 20252
  16. July 20253
  17. June 20252
  18. May 20252
  19. April 20252
  20. March 20251
  21. February 20252
  22. January 20251
  23. November 20241
  24. October 20241
  25. August 20241
  26. June 20241
  27. May 20241
  28. April 20241
    Show
    Coverage in all entries

    64 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →