gitleaks
Auth/lab ref: Gitleaks secret scanning; repo/directory/stdin checks, regex+entropy rules, pre-commit/CI evidence, remediation workflow.
v2026.11.13-21cd5684 instalações+4 em 7 dias39 EstrelasMITsincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/gitleaksGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote80fedb16…4848d2aa
80fedb16b390…12444848d2aa2 arquivos · 4.1 KBVarreduraAlto2 achados
- secret.aws_keyreferences/config-rules.md:34
- Links para domínios externos
Fontegithub.com/AeonDave/malskill/tree/main/offensive-tools/vuln-scanners/gitleaks@21cd568
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
Fast git secrets scanner — API keys, tokens, passwords in repos and files.
Quick Start
# Scan git repository (full history)
gitleaks git /path/to/repo
# Scan directory (no git history)
gitleaks dir /path/to/project
# Scan from stdin
cat file.txt | gitleaks stdin
# With report output
gitleaks git . --report-path results.jsonSubcommands
| Command | Target |
|---|---|
gitleaks git <path> |
Git repository + full history |
gitleaks dir <path> |
Directory or file (no git) |
gitleaks stdin |
Read from stdin |
gitleaks version |
Show version |
Core Flags
| Flag | Purpose |
|---|---|
-c, --config <file> |
Path to .gitleaks.toml config |
-b, --baseline-path <file> |
Baseline of known issues to ignore |
-f, --report-format <fmt> |
Output format: json / csv / sarif / junit |
--report-path <file> |
Save report to file |
-l, --log-level <lvl> |
Log level: debug / info / warn / error |
--exit-code <n> |
Exit code when leaks found (default 1) |
--no-banner |
Suppress banner |
--redact |
Redact secrets in output |
--max-target-megabytes <n> |
Skip files larger than N MB |
--max-decode-depth <n> |
Decode encoded text (base64 etc.) up to N levels |
--max-archive-depth <n> |
Extract and scan archives up to N levels deep |
--no-git |
Treat git repo as plain directory |
--follow-symlinks |
Follow symbolic links |
--log-opts <opts> |
Pass options to git log (e.g. commit ranges, branches) |
--staged |
Scan staged changes (for pre-commit use) |
-v, --verbose |
Show full findings |
Scanning Patterns
# Full history scan
gitleaks git . -v
# Specific commit range
gitleaks git . --log-opts="commitA..commitB"
# Last N commits only
gitleaks git . --log-opts="-n 500"
# Specific branch
gitleaks git . --log-opts="feature-branch"
# Since a date
gitleaks git . --log-opts="--since=2026-01-01"
# CI: scan only new commits in PR
gitleaks git . --log-opts="${CI_COMMIT_BEFORE_SHA}..${CI_COMMIT_SHA}"
# Scan staged changes (pre-commit)
gitleaks git . --staged
# Directory scan (source code, no git history)
gitleaks dir /path/to/project -v
# Scan with custom config
gitleaks git . -c .gitleaks.toml --report-path findings.json
# Decode base64 and scan archives
gitleaks dir . --max-decode-depth=3 --max-archive-depth=2Output Formats
# JSON (richest output)
gitleaks git . --report-format json --report-path report.json
# SARIF (GitHub Advanced Security)
gitleaks git . --report-format sarif --report-path report.sarif
# CSV
gitleaks git . --report-format csv --report-path report.csv
# JUnit XML (CI test reporting)
gitleaks git . --report-format junit --report-path report.xml
# Parse JSON findings:
cat report.json | jq '.[] | {rule: .RuleID, file: .File, secret: .Secret, commit: .Commit, line: .StartLine}'
# List unique rules triggered:
cat report.json | jq -r '.[].RuleID' | sort -u
# Count findings by rule:
cat report.json | jq 'group_by(.RuleID) | map({rule: .[0].RuleID, count: length})'Pre-commit Hook
# .pre-commit-config.yaml
repos:
- repo: https://github.com/gitleaks/gitleaks
rev: v8.24.2
hooks:
- id: gitleaks# Manual hook in .git/hooks/pre-commit:
#!/bin/bash
gitleaks git --pre-commit --staged --verbose
exit $?
# Bypass hook when needed (e.g., legitimate test data)
SKIP=gitleaks git commit -m "message"GitHub Actions
name: Secrets Scan
on: [push, pull_request]
jobs:
gitleaks:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # Full history needed
- uses: gitleaks/gitleaks-action@v2
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}Common Workflows
# Full audit of repo history
gitleaks git . -v --report-path secrets_audit.json
# Fast check before push (same as pre-commit)
gitleaks git . --staged -v
# Scan with baseline (ignore known findings)
gitleaks git . --baseline-path known.json
# Create baseline from current findings (to suppress later)
gitleaks git . --report-path known.json
# Use known.json as baseline going forward
# CI one-liner (non-zero exit = findings found)
gitleaks git . --exit-code 1 --no-banner -q
echo $? # 0 = clean, 1 = secrets found
# Scan without git (plain directory)
gitleaks dir ./src --report-path dir_scan.jsonResources
| File | When to load |
|---|---|
references/config-rules.md |
Custom rule writing, .gitleaks.toml format, entropy tuning, false positive reduction |
Arquivos desta versão
references/15.0 KB
- config-rules.md5.0 KB
- SKILL.md4.8 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Sim | Sim |
| Grava arquivos | Sim | Sim |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- AltaSegredo · secret.aws_keyreferences/config-rules.md:34
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | 80fedb16 | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em Web e bug bounty
Ver a categoriaPergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login