Attributed metadata history
Up to 100 retained publisher events per page for fe158193ba3ac67613a2b19b80908ea605af953c7d89ef528c69fcfc55259faa. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_a748e10085b264ca8e
observed · 2026-10-12 13:41:03 UTC
Changelog 782f310 Archive support (#1872) 489d13c Update README.md d29ee55 Reduce aws-access-token false positives (#1876) 611db65 Set pass_filenames to false for Docker hook (#1850) 0589ae0 unicode decoding (#1854) 82f7e32 Diagnostics (#1856) f97a9ee chore: include decoder in debug log (#1853) Got another @bplaxco release. Cheers! Archive Scanning Sometimes secrets are packaged within archive files like zip files or tarballs, making them difficult to discover. Now you can tell gitleaks to automatically extract and scan the contents of archives. The flag --max-archive-depth enables this feature for both dir and git scan types. The default value of "0" means this feature is disabled by default. Recursive scanning is supported since archives can also contain other archives. The --max-archive-depth flag sets the recursion limit. Recursion stops when there are no new archives to extract, so setting a very high max depth just sets the potential to go that deep. It will only go as deep as it needs to. The findings for secrets located within an archive will include the path to the file inside the archive. Inner paths are separated with !. Example finding (shortened for brevity): Finding
Fingerprint: 744a2004d6f1662c3dd4d13b4e0aec5b940b78e71fed98e7845ae5245c37ed13
intelligence_src_a748e10085b264ca8e
observed · 2026-10-12 13:41:03 UTC
available
Fingerprint: c335ba3d3c7774fc85b6fe21321764b8d03f79cb6a895b335047c91513926933