AI tools, scored for your job
Get paid to train AI
🤝 You're in the Free & Open Source library — community-built tools you can use without paying. A different concept from our scored AI directory.
Home › Free & Open Source › Cybersecurity › Gitleaks
✦ Free & open sourceCybersecurity

Gitleaks

Detect hardcoded secrets like passwords and API keys in git repos.

Scan codebases for hardcoded secrets

Detect API keys, passwords, and tokens across git repositories, files, and standard input.

Free forever · open source · MIT
✓ Use today✓ Browser-based✓ Real-time collaboration
7.4
ZEKAI
Essential secret detection CLI
Free & open source · Cybersecurity
Ease of setup2
Usefulness9
Maintenance9.5
Community9.2
★ 29,223
GITHUB
Sep 2026
UPDATED
MIT
LICENSE
🛠 Don't want to self-host? We can set it up →
⚡ Quick answer

Gitleaks is a command-line tool designed to find leaked secrets in your source code history and file systems. It suits developers and security professionals who need to enforce credential safety in CI/CD pipelines or local workflows.

Runs on
Cross-platform
Hosting
Desktop
Languages
Go
License
MIT

What it is

It parses git commit history using patch analysis, scans static directories, or processes data streamed via stdin. Using regex-based rules and entropy checking, it identifies patterns corresponding to sensitive keys and generates reports in formats like JSON, SARIF, or CSV.

Who it's for

It suits DevSecOps engineers and developers integrating security checks into git hooks or CI pipelines. It does not suit teams looking for active feature expansion, as the creator has marked the project feature-complete and shifted focus to Betterleaks.

Key features

Multiple Scan Modes

Scan local git repositories, individual files, directories, or data streamed via stdin.

Pre-Commit Integration

Catch hardcoded secrets locally before they ever touch remote repositories using pre-commit hooks.

Flexible Reporting

Output scan results in JSON, CSV, JUnit, SARIF, or customized template formats.

Baseline Management

Generate baseline ignore paths to manage existing issues in large or legacy codebases.

How to start

Up and running in 3 steps

1
Install Gitleaks via Homebrew using `brew install gitleaks`, grab a binary from releases, or pull the Docker image.
2
Run a manual scan against your repository directory using `gitleaks git` or `gitleaks dir`.
3
Configure a pre-commit hook by adding the Gitleaks repo config to your `.pre-commit-config.yaml` file.
Real talk

Our honest verdict

What's great

  • Scans past and present git history using log patches
  • Integrates directly into pre-commit workflows and CI/CD pipelines
  • Supports multiple output formats including SARIF and JSON
  • Allows custom configurations and ignore paths via TOML files

Where it falls short

  • Project is feature complete with no new feature merges planned
  • May require tuning rules to reduce false positives depending on codebase
  • Scanning massive repository histories requires manual baseline setup to handle existing noise
Cost

Pricing & license

Free under its open source license, with no paid hosted option provided by the repository. The only cost is running it yourself on your own hardware or CI runner.

Paid work

Open remote AI-training roles

880 open remote AI-training roles, updated November 15, 2026; most pay $20–$175 an hour. Zekai lists them free; the application goes to the employer’s platform.

See all open roles →
Compare

Alternatives

🎁 Free & open-source alternatives

These reviewed AI tools do the same job instantly — from our scored directory.

Get more

Use it, or have us set it up

📄 Free PDF: Gitleaks for Cybersecurity
A plain-language guide to getting your first result. Sent to your inbox.
🔔 64 people want a full video tutorial — add your vote
🛠 Don't want to set it up yourself?
We'll install, host & configure Gitleaks for you — and train your team.
Get it done for you ↗
Questions

FAQ

Is Gitleaks still actively maintained?

Gitleaks is in maintenance mode for security patches only, as the author has shifted focus to Betterleaks.

How can I skip Gitleaks during a git commit?

You can prepend `SKIP=gitleaks` to your git commit command to bypass the check locally.

Radar

Latest AI news

✉️ The weekly free toolkit
The best new free & open-source tools for Cybersecurity — one short email a week, in your language.
Free · 1 email/week · unsubscribe anytime
Get paid to train AI →

See Zekai first in Google