The State of Secrets Sprawl report 2024 is now live!
DOWNLOADDOWNLOAD
GitGuardian logo
Yelp/detect-secrets

Compare GitGuardian to  

Check out how the GitGuardian Platform compares to Yelp/detect-secrets, an open-source secrets scanner.

Quote icon

I've previously implemented open source alternatives. These proved cumbersome, unscalable, and with such large false-positive rates as to make the output useless. That low false-positive rate was one of the reasons we picked it. There are always going to be some, but in reality, it's very low compared to a lot of the other, open source tools that are available.

Andy, Senior Security Engineer at an insurance company with 201-500 employees

Meet the contenders

GitGuardian logo

Meet GitGuardian

GitGuardian is the code security platform for the DevOps generation that offers automated Secrets Detection, Infra as Code Security, and Honeytoken capabilities, facilitating a Secure Software Development Lifecycle for Dev, Sec, and Ops teams.

Yelp/detect-secrets

Meet  

Yelp detect-secrets is a Python CLI and library for detecting secrets within a codebase; it scans files within Git repositories using a pattern matching or entropy filtering technique.

GitGuardian vs.  
The short version

GitGuardian is suitable for you if:

++ In your application security program, you want to address secrets detection and scale it to include all of your company's engineering and security departments.

++ You need a completely integrated platform that goes beyond detection, with features like alerting, incident prioritization, and triage, automated remediation workflows, role-based access management, a REST API, a CLI for developers, etc.

++ You're looking for enterprise-grade software (SaaS or self-hosted) that can manage the continuous monitoring hundreds or thousands of repositories and contributing developers.

++ You are eligible for our free tier, and free and simple to use is great!

  is suitable for you if:

++ Secrets detection is not yet prioritized on your application security roadmap because you first need to size up the issue and its seriousness at your organization.

++ You would prefer to begin with open-source tools and build the missing features later: integrations for source control and alerting, incident lifecycle management, issue tracking, collaboration tools, role-based access management (RBAC), etc.

GitGuardian vs.  
The long version

Core detection capabilities

Regular expressions to match known, distinct patterns

350+ types of specific and generic secrets supported with high accuracy level.

✅ Checks the validity of 200+ types of exposed secrets.

✅ 100+ IaC security policies available out-of-the-box.

✅ Yes, only supports 20 types of secrets out-of-the-box.

✅ Validity checks (fewer than 5 detectors).

❌ No IaC security scanning.

Regular expressions result in fewer false alerts. Additionally, known patterns make it simpler to verify if the secret is true or false or whether this is a test or example key.

Learn more about how GitGuardian detects secrets.

High entropy checks to match credentials without distinct patterns and enter “paranoid” mode

++ Yes, based on the combination of entropy checks and contextual analysis of the presumed secret (pre/post-filters).

++ GitGuardian currently supports 13+ types of generic secrets.

✅ Performs entropy checks to detect generic secrets.

In order to capture a considerably wider variety of secret types, high entropy should be employed.

Learn more about how GitGuardian detects secrets.

Custom patterns

++ Yes, supported with the use of regular expressions (in SaaS/Self-hosted versions).

✅ Yes, the secrets detection engine can be extended with plugins (requires custom development).

To find company-specific secrets that are not picked up by the default patterns, you should be able to define your own patterns.

Learn how to create custom detectors.

Detector activation/deactivation

++ Detectors can be individually activated/deactivated from the UI, in the workspace settings.

✅ Detectors can be deactivated from the command-line.

We recommend keeping all detectors active to avoid missing any hardcoded secrets.

Learn how to configure GitGuardian’s detectors.

Sensitive file names

++ 22 file names raise policy break alerts.

❌ No sensitive file names are detected.

There is a very lengthy list of extensions that potentially hold secrets due to the numerous programming languages, frameworks, and coding standards that are used globally.

Learn which file types contain sensitive information.

Sensitive file extensions

++ 14 extensions raise policy break alerts.

❌ No sensitive file extensions are detected.

Secrets are frequently discovered in file extensions together with environment variables and configuration data. Learn more.

Filepath exclusions

++ Yes, excluding paths is possible through the UI. GitGuardian recommends a set of exclusions (e.g. test directories) and enables users to test filepaths against the active exclusion list.

✅ Yes, excluding paths like test directories is possible using the CLI command flags/options.

The ability to reduce the number of incidents and concentrate solely on those that matter most is critical to scaling your secrets detection and remediation program.

Scanning multiple sources

Code repositories

++ Secrets scanning is possible for local Git repositories or repositories managed through GitHub, GitHub Enterprise, GitLab, Azure DevOps, and Bitbucket Server/Data Center.

✅ Yes, works with local Git repositories.

Your repositories contain secrets and sensitive data, such as user passwords or other security flaws, making it possible for anybody with access to the image to obtain that secret and perhaps exploit it to gain access to other systems.

Learn more on why secrets inside Git are a problem

Docker images

++ Yes, Docker images can be scanned with the GitGuardian CLI, ggshield, using a specific command. The Dockerfile, build arguments, and the image's layers' filesystem are scanned for secrets.

❌ Not supported.

Your Docker image can wind up containing a private SSH key, an AWS access token, or a password.

Learn more about the secrets we found on Docker Hub.

Logs

🟠 The GitGuardian REST API and CLI, ggshield, support scanning all types of text input for secrets. GitGuardian can provide wrappers (code snippets) to extract and load data from observability tools or CI/CD logs.

❌ Not supported natively.

Sensitive data may unintentionally leak from your server logs when services unintentionally output sensitive data.

Other sources

🟠 The GitGuardian REST API and CLI, ggshield, support scanning all types of text input for secrets. GitGuardian can provide wrappers (code snippets) to extract and load data from tools like Slack, Jira, GitHub issues, etc.

❌ Not supported.

Sensitive data may unintentionally be leaked in other productivity tools used by developers.

Monitoring perimeter

GitHub Enterprise
Instance level

++ Yes

❌ No native integration with GitHub Enterprise.

GitHub Enterprise
Organization level

++ Yes, native GitHub App at the organization level (one-click integration).

❌No native integration with GitHub Enterprise.

Repository level

++ Yes, upon integration of a GitHub Enterprise organization, admins can choose to - give access to select repositories - provide access to all repositories (present and future repositories).

❌ No native integration with GitHub Enterprise.

GitHub
Organization or Repository level

++ Yes, native GitHub App available. Admins can:
- give access to select repositories
- give access to all repositories (present and future repositories).

❌ No native integration with GitHub.

GitLab
Instance level

++ Yes, a native integration is available. GitGuardian needs a Personal Access Token with an Admin scope.

❌ No native integration with GitLab.

GitLab
Project or Repository level

++ Yes, a native integration is available. GitGuardian needs a Personal Access Token with an Admin scope to establish a webhook with the VCS for historical and real-time scanning.

❌ No native integration with GitLab.

Bitbucket Server/Data Center
Instance level

++ Yes, a native integration is available. GitGuardian needs a Personal Access Token with an Admin scope to set up a webhook with the VCS for historical and real-time scanning.

❌ No native integration with Bitbucket.

Bitbucket Server/Data Center
Project level

++ Yes, a native integration is available. GitGuardian needs a Personal Access Token with an Admin scope to set up a webhook with the VCS for historical and real-time scanning.

❌ No native integration with Bitbucket.

Azure DevOps (Repos)
Instance level

++ Yes, a native integration is available. GitGuardian needs a Personal Access Token with an Admin scope to set up a webhook with the VCS.

❌ No native integration with Azure Repos.

Azure DevOps (Repos)
Project or Repository level

++ Yes, a native integration is available. GitGuardian needs a Personal Access Token with an Admin scope to set up a webhook with the VCS.

❌ No native integration with Azure Repos.

Secure the SDLC and more

Historical scans

++ Yes, full repository history scan can be launched on-demand. Scanning is performed across all branches and for the entire history up to the initial commit.

✅ Yes, historical scans are run using a CLI command.

Hardcoded secrets can hide deep in the commit history across various branches, not only the latest revision of the code.

Pre-commit

++ Yes, supported through the GitGuardian CLI, ggshield.

✅ Yes, supported out-of-the-box.

Pre-commit hooks put the onus on developers to keep their code free from secrets before contributing to the team’s codebase. The cost of remediation at this stage is low. Learn how to set up a pre-commit hook with GitGuardian.

Pre-push

++ Yes, supported through the GitGuardian CLI, ggshield.

✅ Yes, supported via customization.

Pre-push hooks put the onus on developers to keep their code free from secrets before contributing to the team’s codebase.

Pre-receive

++ Yes, supported through the GitGuardian CLI, ggshield.

In addition, a 'break-glass' option is provided to avoid blocking developer workflow in case test credentials or false positives are raised.

✅ Yes, supported via customization.

Pre-receive hooks are the most effective tool to prevent secrets from reaching your codebase.

Post-receive

✅ Yes, supported with the native VCS integrations (GitHub, GitLab, Bitbucket and Azure DevOps). Historical and continuous protection.

❌ No native integrations with the VCS for continuous scanning.

CI environment

++ Yes, the GitGuardian CLI, ggshield, runs natively with 8 different providers in total: GitHub Actions, GitLab CI/CD, Bitbucket pipelines, Azure pipelines, Jenkins CI, CircleCI, Drone CI, and Travis CI.

✅ Yes, can be performed via customization of the detect-secrets CLI.

It is important to raise awareness around the problem of hardcoded secrets and align Dev, Sec, and Ops with Automated Security Testing (AST) in pipelines.

Learn how to use GitGuardian's secrets detection in your CI workflows.

Pull requests (check runs)
& commit status checks

++ In GitHub, secrets scanning check runs can be triggered on pull requests on repositories monitored by GitGuardian. The behavior can be configured to block merging PRs containing secrets.

❌ Not supported.

Pull request or merge request scanning brings secrets detection to environments developers are familiar with, such as the GitHub or GitLab UI.

Enriched UI and centralization of incidents

Rich UI with all data needed for investigation and remediation

++ Unified view of incidents across all monitored sources found via the native VCS integrations.

❌ Not available.

It facilitates the collection of relevant data for big-picture analysis.

Security team view
(global view)

++ Rich UI/centralized dashboard for Security and Incident Response teams.

❌ Not available.

To accurately assess the code security posture of an enterprise, security professionals require visibility across complex, sprawling environments.

Developer/Engineering view (local view)

++ Developers can get access to incidents via the GitGuardian UI, with a scoped view on incidents shared with them.

++ An external page can be generated for the developers to view individual incident details, fill out a feedback form and possibly remediate the incident on their own with our advice.

❌ Not available.

Developers can view and handle their incidents most effectively with the help of intuitive dashboards.

Incident Lifecycle Management

Incident data

✅ In addition to data such as the commit sha, date, author, secrets type, location (repository, file name, line) and validity, GitGuardian provides contextual tags such as "from a historical scan", "sensitive file", "test file", "exposed publicly", "leaked publicly", "regression", "default branch", etc. 

❌ Not available.

Incident data helps you in prioritizing and investigating incidents better by giving additional context.

Automated Severity Scoring

++ GitGuardian scores the severity of incidents: "Low", "Medium", "High" or "Critical" following default rules or user-defined rules.

❌ Not available.

Severity scoring will assist in identifying and prioritizing issues for quicker resolution.

Validity and presence checks

++ For certain secrets, GitGuardian can perform non-intrusive checks to verify their validity. When revoked, secrets will be marked as no longer valid, effectively providing proof of remediation.

++ GitGuardian can also verify the presence of the secrets in the commits and provide proof of deletion after all evidence of the secret is removed.

❌ Not available.

Users should be able to check the validity of each incident and determine whether the leaked secret is still present or has been entirely erased from the commit history. Learn how to verify if an exposed secret was removed from the commit history.

Occurrence grouping

++ GitGuardian groups all occurrences of the same secret leak across files, repositories, and organizations.

❌ Not available.

You can lessen alert fatigue. There is no need to triage/resolve each and every occurrence separately.

Incidents status management

++ Incident handling with "Triggered", "Assigned", "Resolved" and "Ignored" statuses. Two outcomes are possible: incidents can be resolved or ignored.

❌ Not available.

This will assist organizations in swiftly identifying incidents and mitigating their negative impact.

Incident assignment

++ Incidents can be assigned to a team member (a security engineer or a developer) to handle the incident.

❌ Not available.

Defining incident assignees makes sure that the incident gets a timely and appropriate response.

Remediation guidelines

++ Default remediation guidelines and recommendations are displayed in the UI. The guidelines can also be customized.

❌ Not available.

You have some remediation guidelines by default. But as each organization has its own context and remediation policies, you will have the ability to customize the remediation guidelines.

Learn how to create custom remediation guidelines.

Automation and playbooks

++ Incident remediation playbooks like sharing incidents with involved developers, collecting feedback, and closing incidents when they are re-checked as invalid can be automated.

❌ Not available.

The time savings, particularly at the enterprise scale, can be significant. Playbooks keep your teams productive and focused!

Learn more about how to prioritize, investigate and remediate hardcoded secrets incidents at scale.

Incident timeline

++ A detailed timeline is provided with an extensive activity log of all performed events (status changes, feedback notes, access sharing, and much more).

❌ Not available.

Timelines help security teams keep track of all of the actions performed on the incident.

Collaboration with developers

++ Developers can get access to incidents via:
• GitGuardian workspace, scoped view on incidents shared with them;
• A link to an external page can be generated for the developers to view individual incident details, fill a feedback form and possibly remediate the incident on their own.

❌ Not available.

Because developers are key to taming secrets sprawl, AppSec teams must provide them with instant access to and ownership of their hardcoded secrets incidents.

Learn how to bring Dev, Sec, and Ops together for tackling secret sprawl.

Whitelisting options

++ Yes. When ignoring incidents, it is possible to flag findings as false positives, low-risk credentials, or test credentials.

✅ Yes.

Pull request or merge request scanning brings secrets detection to environments developers are familiar with, such as the GitHub or GitLab UI.

Regression behavior

++ New occurrences of a resolved incident can be configured to re-open the incident and trigger new alerts or deliver silent notifications.

❌ Not available.

If new secrets were added or rotated secrets broke existing app functionality, you need to reopen the incident.

Alerting

Real-time alerting

++ Yes

❌ Not supported.

Serious incidents are immediately identified. Alerts may be directed to the right developers more rapidly for remediation.

Email alerts

++ Yes, to prevent alert fatigue, only one email is sent for multiple occurrences of the same incident.

❌ Not supported.

The problem of secret leaks has developers at the forefront. It is crucial to notify the developer in charge of the incident via their commit email.

Learn what's included in GitGuardian email alerts.

Integration with most common SIEMs like Splunk or ITSMs

++ Yes

❌ Not supported.

Teams, processes, and tools should be integrated to increase efficiency and effectiveness for all users by ensuring that alerts are received at the appropriate time and location and that no alert is missed.

Integration with ticketing systems like Jira or messaging apps like Slack

++ Yes

❌ Not supported.

By integrating your code security platform and ticketing/messaging tool, you can address critical incidents and expedite remediation.

Event-driven generic webhooks

++ Yes

Stay in the know with event-driven alerts when new incidents are raised or when actions are performed on open incidents.

Reporting & Analytics

Analytics

++ Yes, enriched analytics to assess security posture over time and remediation performance.

❌ Not available.

Analytics help you assess security posture over time, and remediation performance.

Data exports

++ All data is exportable in .csv (including historical incidents) or in JSON format using the REST API.

❌ Not available.

Your Dev can review the incident data and filter it further based on their needs.

Enterprise support

Deployment

++ SaaS & On-premises (self-hosted)

✅ Self-hosted open-source CLI and SDK.

SaaS is less expensive and easier to scale, while on-premises offers more visibility.

See how an enterprise customer deployed a secrets detection program.

SSO

++ Yes, fully compatible with any SAML 2.0 provider.

❌ Not available.

Because users only log in once per day and utilize a single set of credentials, it decreases the number of attack surfaces.

See the setup procedures for different IdPs.

Roles Based Access Control (RBAC) & Team management

++ Yes, the available roles "Workspace Owner", "Manager" (admin), "Member" and "Restricted" are designed for fine-grained access control down to the occurrence level. Teams management available.

❌ Not available.

It's a wonderful approach to bring in every developer, scale up incident remediation, and deal with orphan incidents.

Learn how RBAC can help fix hardcoded credentials faster.

Audit logs

++ Detailed activity logs of all actions triggered on the dashboard or through the REST API.

❌ Not available.

Audit logs include precise historical data that can be used to retrace an incident's timeline.

See how to access Gitguardian audit logs.

REST API

++ GitGuardian’s public REST API can be used to realize all sorts of actions on your workspace and incidents (retrieve, assign, update status, and share secrets incidents, and more).

❌ Not available.

This API provides you with access to all of the incident data, including tasks.

Enterprise support & onboarding

++ A dedicated team of Solutions and DevOps Engineers will be made available to help you rollout secrets detection and remediation for your organization (included in the licensing model, at no additional cost).

❌ Not available.

In order to use a product effectively, a solid onboarding program aids in your ability to comprehend and experience the value it offers.

It is always advantageous to have support professionals who are completely committed to fixing any technical issues you may encounter.

Read more in-depth articles on GitGuardian Blog.

Why does it matter?

OFFERS
PARTIALLY OFFERS
DOES NOT OFFER

{{group.name}}

Toggle

v-html being used here

v-html being used here

v-html being used here

v-html being used here

Note: The space is evolving quickly, and we do our best to keep information on our competitors up to date. If you see any outdated information, contact us and we will immediately set the record straight!

How do users like you rate us?

Users rate GitGuardian high on these categories on review sites like PeerSpot, G2, and Capterra.

Ease of Use • 4.6 stars

Customer Service • 4.6 stars

Value for Money • 4.6 stars

Ease of Use • 8.9

Quality of Support • 9.0

Ease of setup • 9.3

Top 6 reasons why users choose GitGuardian over Yelp/detect-secrets for their code security

While open-source solutions like Yelp Detect Secrets can be a good choice for some organizations, they may not be the best fit for everyone. It's important to carefully consider the specific needs and requirements of your organization before choosing a code security solution.

Open source projects rely on volunteers for maintenance and development, which can lead to inconsistent updates and bug fixes. Yelp detect-secrets requires ongoing maintenance and upkeep, including regular updates and scans of your codebase. This can be time-consuming and may need a dedicated resource.

GitGuardian is available as a service too, so there is no maintenance required.

GitGuardian has the GUI that Yelp detect-secrets doesn't have. 

GitGuardian’s rich UI and analytics dashboard allow Dev, Sec teams, and Ops to collaborate. You can start scans and check their results, assign open secret incidents to developers in your team with restricted roles, track progress with analytics, etc. Our Incidents Details view captures the entire scene of the secret incident and helps you in further investigation.

Compared to GitGuardian's secrets detection engine which incorporates over 350 specific and generic detectors, Yelp/detect-secrets' 20 detectors are inadequate for efficient detection, resulting in the need to construct additional detectors manually.

The use of generic detectors is essential in detecting all valid secrets, and GitGuardian's detection engine performs secret validity checks and contextual code analysis to eliminate false positives. Additionally, GitGuardian consolidates multiple occurrences of secrets exposed in various files and repositories into a single incident.

Yelp detect-secrets is a stand-alone solution that may not integrate well with other security tools, limiting its ability to provide a comprehensive security picture.

In contrast, GitGuardian is VCS agnostic, offering native integrations with various platforms and the ability to receive alerts directly in Slack or Discord. You can also report incidents to Jira and Pagerduty or create custom webhooks, enabling integration with your existing workflows.

Yelp detect secrets does not cover incident response and remediation.

GitGuardian offers playbooks to help organizations respond quickly and effectively to incidents. Sec engineers can automate alerting, ticketing, severity scoring, prioritizing, and collaboration tasks with developers using GitGuardian playbooks. With our customized remediation advice, developers can prioritize and eliminate the majority of high-severity incidents in a matter of hours.

As an open source tool, there may be limited official support available to you, compared to commercial solutions. Their documentation also may not be as complete as commercial solutions, making it harder for you to get started and use the tool effectively.

GitGuardian offers a wide range of customer support services, including Proof-of-Concept (PoC) exercises, phased rollout, and scaling, simple implementation with onboarding programs, specialized technical account managers for ongoing check-ins, etc.

GitGuardian is the #1 security application on the GitHub Marketplace

Trusted by security leaders
at the world’s biggest companies

Learn how Jon-Erik and his team saved over 200 hours of manual review

The solution has significantly reduced our mean time to remediation, by three or four months. We wouldn't know about it until we did our quarterly or semi-annual review for secrets and scan for secrets.

Jon-Erik Schneiderhan, Senior Site Reliability Engineer at a computer software company with 501-1,000 employees

Read the case study

Want to see the difference for yourself?

And keep your secrets out of sight