Detect hardcoded secrets like passwords and API keys in git repos.
Detect API keys, passwords, and tokens across git repositories, files, and standard input.
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.
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.
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.
Scan local git repositories, individual files, directories, or data streamed via stdin.
Catch hardcoded secrets locally before they ever touch remote repositories using pre-commit hooks.
Output scan results in JSON, CSV, JUnit, SARIF, or customized template formats.
Generate baseline ignore paths to manage existing issues in large or legacy codebases.
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.
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.
These reviewed AI tools do the same job instantly — from our scored directory.
Gitleaks is in maintenance mode for security patches only, as the author has shifted focus to Betterleaks.
You can prepend `SKIP=gitleaks` to your git commit command to bypass the check locally.
See Zekai first in Google