Update pre-commit hook gitleaks/gitleaks to v8.27.2 #516
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v8.26.0->v8.27.2Note: The
pre-commitmanager in Renovate is not supported by thepre-commitmaintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
gitleaks/gitleaks (gitleaks/gitleaks)
v8.27.2Compare Source
Changelog
c7acf33Merge branch 'master' of github.com:gitleaks/gitleaks9faaa4aAdd experimental allowlist optimizations (#1731)79068b3Detect Notion Public API Keys #1889 (#1890)v8.27.1Compare Source
Changelog
80468efMerge branch 'master' of github.com:gitleaks/gitleaksef82237fix(atlassian): reduce false-positives for v1 pattern (#1892)2463f11Fix log suppresion issue (#1887)6f251eeAdded Heroku API Key New Version (#1883)20f9a1dAdd Platform Bitbucket (#1886)722ce82Add Platform Gitea (#1884)79780b8Merge branch 'master' of github.com:gitleaks/gitleaksc5683caprevent default warn message when max-archive-depth not set (#1881)0357c3cprevent default warn message when max-archive-depth not setv8.27.0Compare Source
Changelog
782f310Archive support (#1872)489d13cUpdate README.mdd29ee55Reduce aws-access-token false positives (#1876)611db65Setpass_filenamestofalsefor Docker hook (#1850)0589ae0unicode decoding (#1854)82f7e32Diagnostics (#1856)f97a9eechore: 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-depthenables this feature for both
dirandgitscan 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-depthflag sets the recursion limit. Recursion stops whenthere 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):
This means a secret was detected on line 4 of
files/.env.prod.which is inarchives/files.tarwhich is intestdata/archives/nested.tar.gz.Currently supported formats:
The compression
and archive
formats supported by mholt's archives package
are supported.
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.