Attributed metadata history
Up to 100 retained publisher events per page for d22af1d0c7ace34a2446bdf15e8d7d4ced2a35f303552b3e1385b66b2142faf7. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_a748e10085b264ca8e
observed · 2026-10-12 13:41:03 UTC
Changelog 4fb4382 cant count b1c9c7e Composite rules (#1905) 72977e4 feat: add Anthropic API key detection (#1910) 7b02c98 fix(git): handle port (#1912) 2a7bcff dont prematurely calculate fragment newlines (#1909) bd79c3e feat(allowlist): promote optimizations (#1908) 7fb4eda Fix: CVEs on go and go crypto (#1868) a044b81 feat: add artifactory reference token and api key detection (#1906) bf380d4 silly f487f85 Update gitleaks.yml 958f55a add just like that, no leaks Optimizations #1909 waits to find newlines until a match. This ends up saving a boat load of time since before we were finding newlines for every fragment regardless if a rule matched or not. #1908 promoted @rgmz excellent stopword optimization Composite Rules (Multi-part or required Rules) #1905 In v8.28.0 Gitleaks introduced composite rules, which are made up of a single "primary" rule and one or more auxiliary or required rules. To create a composite rule, add a [[rules.required]] table to the primary rule specifying an id and optionally withinLines and/or withinColumns proximity constraints. A fragment is a chunk of content that Gitleaks processes at once (typically a file, part of a file, or git diff), and proximi
Fingerprint: cca3413786e4480755473f043ff37d79429717872fc75f730e059da146bc5a47
intelligence_src_a748e10085b264ca8e
observed · 2026-10-12 13:41:03 UTC
available
Fingerprint: c335ba3d3c7774fc85b6fe21321764b8d03f79cb6a895b335047c91513926933