Gitleaks
Secret detection tool to find exposed credentials in code and repositories.
0 members list Gitleaks, unchanged over the last 12 weeks, data as of 14 November 2026
Members who list Gitleaks in their Stack, by week.
Members who list Gitleaks
Be the first to add Gitleaks
Nobody on Stackness runs Gitleaks yet. Add it to your stack and you're the first member running it.
Homebrew analytics installs: 11,315 installs (2026) to 18,966 installs (2026)
Imported from Homebrew analytics, last reading Oct 2026
About Gitleaks
Gitleaks is an open-source secret scanner that searches git repositories, files, and directories to find exposed credentials and sensitive information. Developers use it to prevent secrets like API keys and passwords from being accidentally committed to version control. The tool can be integrated into continuous integration and continuous deployment workflows to automatically scan pull requests and commits.
Gitleaks is developed by gitleaks and released under the MIT license. It is written in Go and available through multiple distribution channels including Docker, GitHub releases, and package managers. A GitHub Action is available for teams using GitHub that want to run automated scans on repositories. Personal GitHub accounts can use the tool without a license key, while GitHub organization accounts require a free license key obtained through the project.
Checked 10 November 2026.
Nobody on Stackness runs Gitleaks yet.
Sign up and add itPosts about Gitleaks
- Verify what a coding agent claims it deployed: the live commit, a Stop hook and the files it wrote
Check an agent's deploy by comparing the commit the live server reports with HEAD, using a check it did not write. Asking it to recheck fixes 1 failure in 3.
- Where API keys leak with AI coding agents: the files, the tests and the caps that limit the bill
Confirmed agent-stack key leaks in October 2026 ran through agent configs and hosted services, not .env. Where keys sit, how to test, and the caps.
- Can a coding agent find vulnerabilities in your codebase? Where the security pass goes: pre-commit, pull request or schedule
Agents found the PHP bugs fixed on 21 October 2026, but on real apps 82-86% of agent findings were false. Three security layers, with commands.