Gitleaks

What's new:

• Change whitelist to allowlist. This is a breaking change. v5.0.0 custom configs will need to be updated.
• Line numbers have been added to the report. This has been a requested feature by many and I'm happy to include it in this release. There is a slight performance hit if leaks are present due to the fact that in order to extract the line number Gitleaks has to do a reverse search on a file/commit/patch depending on the scan conditions.
• Git additions only are now scanned by default. Scanning additions by defaults makes the most sense since users mainly care about when a leak has been introduced, not necessarily removed. Deletions can be included with the --include-deletion option.
• Operation added to the report. This is the git operation (addition/equal/deletion) associated with a leak.
• Bumped gitleaks module to v5.
• go-git has been bumped to v5.10.0

What's fixed:

• The patch direction was wrong. Gitleaks was patching currentCommit.Patch(parent) rather than the correct parent.Patch(currentCommit). This had the side effect of reporting the wrong commit sometimes. In v5.0.0 this has been fixed.