Skip to content
Dev Tools Library

Gitleaks

Detects leaked secrets in code and Git history.

CLIOpen source

Scans repositories and commits for API keys, passwords and tokens, and can run in hooks and in CI.

When to use

To keep keys and passwords out of the repository, in pre-commit hooks and in CI.

When to avoid

As your only defense: secrets that already leaked must be revoked, not just removed.

Alternatives

They do a similar job. Compare before choosing.

  • Finds and verifies leaked secrets in repositories and other sources.

    CLIOpen source★ 28.8K

From the same area, with a close purpose.

  • GitHub's native dependency updates and alerts.

    ServiceFree