Gitleaks

What's New:

• https://github.com/zricethezav/gitleaks/pull/480 I forked go-git and made some specific operations thread safe. See https://github.com/zricethezav/go-git/releases/tag/v5.2.1. This allows for concurrent patch generation which speeds up scans significantly. As a large repo benchmark, I often use https://github.com/rails/rails.

Below are some results: v7.1.0: gitleaks --repo=https://github.com/rails/rails --threads=12

INFO[0000] cloning... https://github.com/rails/rails
INFO[0134] scan time: 1 minute 51 seconds 828 milliseconds 144 microseconds
INFO[0134] commits scanned: 89801
WARN[0134] leaks found: 4

v7.0.2: gitleaks --repo=https://github.com/rails/rails --threads=12

INFO[0000] cloning... https://github.com/rails/rails
INFO[0239] scan time: 3 minutes 36 seconds 45 milliseconds 232 microseconds
INFO[0239] commits scanned: 89801
WARN[0239] leaks found: 4

• https://github.com/zricethezav/gitleaks/pull/481 Let's talk exit codes... again. I'm trying to follow the convention defined here: https://tldp.org/LDP/abs/html/exitcodes.html. But it seems that people expect exit codes to behavior differently. So, I'm adding a --leaks-exit-code flag:

--leaks-exit-code=  Exit code when leaks have been encountered (default: 1)

The default codes:

0 - no leaks found
1 - leaks or errors encountered