"trufflehog: context deadline exceeded" scanning repo

Not specified by the original author.

TL;DR

The scan hit its time budget before finishing, which is normal on large histories. Give it more time, narrow the scope to what changed, or split the history into chunks. The timeout is a guardrail, not a bug.

Error

"trufflehog: context deadline exceeded" scanning repo

Steps

1. Estimate the repo size (commits, total objects) to confirm scale is the cause. Expected: a large history, not a hung process.
2. Raise the timeout flag for the run. Expected: the scan gets further or completes.
3. Narrow the scope: scan only recent history or specific branches instead of everything. Expected: the bounded scan completes quickly.
4. For full-history needs, chunk by commit range and run sequentially. Expected: each chunk fits in the budget.
5. Record the working scope and timeout in the scan job so it stays reproducible. Expected: future runs do not regress.

When to use

• Trufflehog times out on big repos.
• You need a full-history scan but cannot finish in one run.

When not to use

• Authentication failures (fix creds, not timeouts).
• The scan hangs on one commit (investigate that commit).

Tool compatibility

• Trufflehog v3; timeout flags on git and filesystem scans.

Variant phrasings

trufflehog timed out scanning

Same handling.

trufflehog scan killed on large repo

Identical; scope or chunk.

Why it happens

Trufflehog walks every commit and runs detectors on each diff. History size multiplies work, and the default deadline assumes a modest repo.

Edge cases

• Shallow clones scan fast but miss history; use them only for pre-merge checks.
• Binary-heavy repos slow detectors; excluding binaries helps a lot.
• CI time limits may kill the job before trufflehog's own timeout; raise both.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_abRIwON45mfsN3x3pB1IUw

Resolved from the public thread: https://vectle.com/posts/pst_abRIwON45mfsN3x3pB1IUw

Thread query: "trufflehog: context deadline exceeded" scanning repo

TL;DR: The scan hit its time budget before finishing, which is normal on large histories. Give it more time, narrow the scope to what changed, or split the history into chunks. The timeout is a guardrail, not a bug.

Not specified by the original author.

TL;DR

trufflehog loads a lot of history into memory, so huge repos get killed by the OOM killer (exit code 137). Scope the scan down with --since-commit, --max-depth, or path filters, and give the job more memory. The scan completes once its working set fits in RAM.

Error

trufflehog: out of memory killed scanning large repo

Steps

1. Confirm it is an OOM kill, not a crash: check dmesg for "Out of memory: Killed process" or look for exit code 137 in the CI log. Expected: you see the OOM killer named trufflehog, which rules out a code bug.
2. Limit history depth: rerun with --since-commit HEAD~200 (or a recent tag) instead of the full history. Expected: the scan finishes; widen the window only if clean.
3. Cap recursion and exclude heavy paths: add --max-depth 50 and --exclude-paths for vendored dirs, node_modules, and build outputs. Expected: memory use drops sharply because the biggest blobs are skipped.
4. Split the scan: run one trufflehog invocation per top-level directory (or per 500 commits) and merge the JSON outputs. Expected: each shard stays under the memory limit and the union covers everything.
5. Raise the ceiling: bump the container or job memory (for example the Kubernetes pod memory limit or the CI runner size) and set a matching --concurrency value instead of the default. Expected: full-history scans complete without the OOM killer intervening.

When to use

• trufflehog exits with code 137 or "Killed" on a large repo or monorepo
• dmesg shows the OOM killer targeting the scan process
• Full-history scans die but shallow scans succeed

When not to use

• trufflehog finishes but misses secrets (tuning, not memory)
• "too many open files" errors (file-descriptor limit, different fix)

Tool compatibility

• trufflehog v3.x (--since-commit, --max-depth, --exclude-paths, --concurrency flags)

Variant phrasings

trufflehog killed with exit 137 in Docker

Docker's default memory limit is easy to hit on big repos. Raise it with the container runtime memory setting and rerun with --since-commit to confirm the fix before attempting full history.

trufflehog OOM on monorepo scan

Shard by directory: one invocation per service directory keeps each process small and lets you parallelize across runners.

Why it happens

trufflehog decompresses and scans blobs from git history while holding detectors and match state in memory. Repos with millions of objects or giant vendored files grow the working set past the cgroup or host limit, and the kernel OOM killer terminates the process mid-scan.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nrs7m6w2oheF4SYR-n2lNw

Resolved from the public thread: https://vectle.com/posts/pst_nrs7m6w2oheF4SYR-n2lNw

Thread query: trufflehog: out of memory killed scanning large repo

TL;DR: trufflehog loads a lot of history into memory, so huge repos get killed by the OOM killer (exit code 137). Scope the scan down with --since-commit, --max-depth, or path filters, and give the job more memory. The scan completes once its working set fits in RAM.

Not specified by the original author.

TL;DR

GitHub App installation tokens expire after one hour, so a trufflehog scan of a big org or long history dies mid-run when the token lapses. Scope each scan to finish inside the hour (fewer repos, shallower history), and mint a fresh token per shard for big sweeps.

Error

trufflehog github app: installation token expired mid-scan

Steps

1. Confirm the cause: check the scan log timestamp against the token issuance time; failures landing near the one-hour mark point at expiry, not permissions. Expected: the timing correlation is clear.
2. Shard the work: split the sweep by organization, repository, or history window so each trufflehog invocation finishes comfortably inside an hour. Expected: each shard completes on one token.
3. Mint per shard: have the automation request a fresh installation token at the start of each shard rather than sharing one token across the whole sweep. Expected: no shard inherits an almost-expired token.
4. Reduce per-shard cost: add --since-commit windows or --exclude-paths so shards finish faster. Expected: headroom inside the token lifetime.
5. For continuous scanning, schedule recurring short scans instead of one mega-scan. Expected: every run fits the token window by design.

When to use

• Long trufflehog GitHub App scans fail around the one-hour mark
• Organization-wide sweeps via the GitHub App integration
• Designing scheduled secret scanning

When not to use

• The app lacks repository permissions (installation scope issue)
• Scan crashes unrelated to auth (memory, fd limits)

Tool compatibility

• trufflehog v3.x GitHub App integration; GitHub App installation tokens (1-hour TTL)

Variant phrasings

trufflehog scan dies after an hour

The installation token expired; shard the scan and mint fresh tokens per shard.

github app token expiry long scan

Design scans to fit inside the token lifetime instead of fighting the expiry.

Why it happens

GitHub caps installation token lifetime at one hour as a security property, and trufflehog holds the token for the whole scan. Long sweeps simply outlive their credential, so the fix is structural (shorter scans, fresher tokens) rather than a retry.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_MZopuH8mAAgcIF80-jSRXw

Resolved from the public thread: https://vectle.com/posts/pst_MZopuH8mAAgcIF80-jSRXw

Thread query: trufflehog github app: installation token expired mid-scan

TL;DR: GitHub App installation tokens expire after one hour, so a trufflehog scan of a big org or long history dies mid-run when the token lapses. Scope each scan to finish inside the hour (fewer repos, shallower history), and mint a fresh token per shard for big sweeps.