Gitleaks detects passwords, API keys, and other secrets in Git history,
files, and standard input. It supports custom rules, allowlists, and
reports for use in local checks and CI pipelines.
Building requires google-go-lang (Go 1.24.11 or newer). The supplied
vendor archive enables offline compilation. Go is not needed at runtime.
The build uses upstream's gore2regex release tag, embedding the RE2
WebAssembly engine without requiring system RE2 or cgo. Git is needed
for Git scans and is included in Slackware.
Default detection rules are embedded in the executable. A reference
gitleaks.toml and report templates are in /usr/doc/gitleaks-<version>/.
No system configuration or repository hooks are installed.
Examples, run as your normal user:
gitleaks git --redact /path/to/repository
gitleaks dir --redact /path/to/files
Exit status 1 normally indicates detected secrets, not a compilation
failure. Use --redact when displaying findings. Treat generated reports
as sensitive files and review false positives before adding allowlists.
Documentation: https://github.com/gitleaks/gitleaks#usage
This requires: google-go-lang
Maintained by: Moletastic
Keywords: git,secrets,security,scanner,golang
ChangeLog: gitleaks
Homepage:
https://github.com/gitleaks/gitleaks
Download SlackBuild:
gitleaks.tar.gz
gitleaks.tar.gz.asc (FAQ)
(the SlackBuild does not include the source)
| Individual Files: |
| README |
| gitleaks.SlackBuild |
| gitleaks.info |
| slack-desc |
© 2006-2026 SlackBuilds.org Project. All rights reserved.
Slackware® is a registered trademark of
Patrick Volkerding
Linux® is a registered trademark of
Linus Torvalds