pickfit

BrowseSecurity & networking tools

Gitleaks

Command-line tool that detects secrets such as passwords, API keys and tokens in git repositories, files and stdin.

Use it

Before you install: known vulnerabilities

pickfit found 13 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • go:github.com/andybalholm/brotli v1.2.0 Excessive memory allocation when decompressing crafted streams in github.com/andybalholm/brotli (GO-2026-6888, critical, fixed in 1.2.7)
  • go:golang.org/x/crypto v0.35.0 golang.org/x/crypto vulnerable to auth bypass via unenforced @revoked status (GHSA-5cgq-3rg8-m6cv, critical, fixed in 0.52.0)
See 8 more

3 more findings not listed here.

Linux x86_64

You need first

  • Runtimes: go (for building from source)
  1. Download the v8.30.1 linux_x64 release tarball and install the gitleaks binary into ~/.local/bin

    mkdir -p ~/.local/bin /tmp/gl && curl -fsSL -o /tmp/gl/gl.tgz https://github.com/gitleaks/gitleaks/releases/download/v8.30.1/gitleaks_8.30.1_linux_x64.tar.gz && tar -xzf /tmp/gl/gl.tgz -C /tmp/gl && install -m 755 /tmp/gl/gitleaks ~/.local/bin/gitleaks

Check that it works

gitleaks version

The output should contain “8.30.1”.

First thing to try

gitleaks version

Run gitleaks version to confirm it is installed, then gitleaks dir -v <path> to scan files.

What it does

  • Scan directories or files for secrets
    How to use it
    1. Run gitleaks dir -v <path> on a file or directory.
    2. Read each finding's rule ID, file, line and fingerprint in the output.
    Tested
  • Find secrets in text piped from stdin
    How to use it
    1. Pipe text into Gitleaks with cat <file> | gitleaks -v stdin.
    2. Check the RuleID of each finding to see what kind of secret was found.
    Tested
  • Write your own secret detection rules
    How to use it
    1. Create a TOML config file with a [[rules]] entry that sets an id, description, regex and keywords.
    2. Scan with your rules using gitleaks dir -v --config <config.toml> <path>.
    Tested
  • Scan git repositories for secrets
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 3 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • scan a local git repository history for leaked secrets
  • block commits containing secrets with a pre-commit hook
  • run secret scanning in CI as a GitHub action
  • scan directories or files for secrets

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version 8.30.1

Differences the test machine hit

  • README: From Source (make sure `go` is installed): git clone ...; cd gitleaks; make build
    In the test: Go is not available in this box and may not be installed here, so I used the prebuilt release binary (gitleaks_8.30.1_linux_x64.tar.gz) from the releases page that the README links to.
  • README: --exit-code int exit code when leaks have been encountered (default 1)
    In the test: Scans that find secrets exit 1 by default. That is expected, not an error. Use --exit-code 0 if a pipeline needs exit 0.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.