pickfit

BrowseSecurity & networking tools

TruffleHog

Command-line tool that finds leaked credentials in git repos, cloud storage, filesystems and other sources, and checks whether they are live.

Use it

Before you install: known vulnerabilities

pickfit found 3 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/docker/docker v28.5.2+incompatible Docker: Race condition in docker cp allows bind mount redirection to host path (GHSA-rg2x-37c3-w2rh, high, no fix yet)
See 2 more
  • go:github.com/docker/docker v28.5.2+incompatible — GHSA-x86f-5xw2-fm2r (high), no fix yet
  • go:github.com/docker/docker v28.5.2+incompatible — GO-2026-4887 (high), no fix yet

Linux x86_64

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. download the official install.sh (read before running)

    curl -sSfL https://raw.githubusercontent.com/trufflesecurity/trufflehog/main/scripts/install.sh -o /tmp/install.sh
  2. run install.sh with -b ~/.local/bin, which installs trufflehog v3.99.9 after checking its sha256

    sh /tmp/install.sh -b "$HOME"/.local/bin
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

curl -sSfL https://raw.githubusercontent.com/trufflesecurity/trufflehog/main/scripts/install.sh -o /tmp/install.sh
sh /tmp/install.sh -b /home/sbx/.local/bin
trufflehog --version
mkdir -p /home/sbx/work/scan/dir && cat > /home/sbx/work/scan/file1.txt <<'EOF'
[default]
aws_access_key_id = AKIAQX7RZ4MWT2LBNV6K
aws_secret_access_key = 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
EOF
cat > /home/sbx/work/scan/dir/config.env <<'EOF'
GITHUB_TOKEN=ghp_R7tKq2LmX9vB4nWc8Zp1Hs6Jd3Fy5Ga0Ue7T
EOF
trufflehog filesystem scan/file1.txt scan/dir --no-verification --no-update

Check that it works

trufflehog --version

The output should contain “trufflehog 3.99.9”.

First thing to try

mkdir -p "$HOME"/work/scan/dir && cat > "$HOME"/work/scan/file1.txt <<'EOF'
[default]
aws_access_key_id = AKIAQX7RZ4MWT2LBNV6K
aws_secret_access_key = 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
EOF
cat > "$HOME"/work/scan/dir/config.env <<'EOF'
GITHUB_TOKEN=ghp_R7tKq2LmX9vB4nWc8Zp1Hs6Jd3Fy5Ga0Ue7T
EOF
trufflehog filesystem scan/file1.txt scan/dir --no-verification --no-update

Run trufflehog filesystem <path> --no-verification --no-update to scan local files or folders for secrets.

What it does

  • Find secrets in git, chats, wikis and buckets
    How to use it
    1. Scan files or folders with trufflehog filesystem <file> <dir> --no-verification --no-update.
    2. Scan a local git repository with trufflehog git file://<repo> --no-verification --no-update.
    3. Scan a remote repository with trufflehog git <repo-url> --results=verified --no-update.
    Tested
  • Identify over 800 types of secrets
    How to use it
    1. Run trufflehog filesystem <file> <dir> --no-verification --no-update.
    2. Read the Detector Type line in each result to see what kind of secret was found.
    Tested
  • Check whether found credentials still work
    How to use it
    1. Run trufflehog git <repo-url> --results=verified --no-update to show only credentials confirmed as live.
    2. Look for "Found verified result" in the output.
    Tested
  • Analyze permissions of leaked API keys
    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 git repository for verified secrets
  • scan an S3 bucket for leaked credentials
  • scan a Docker image for secrets
  • check pull request branches for secrets in CI
  • scan local files or directories for credentials

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 3.99.9

Differences the test machine hit

  • README: curl ... install.sh | sh -s -- -b /usr/local/bin
    In the test: -b /home/sbx/.local/bin, because /usr/local/bin cannot be written without root
  • README: Expected output shows AWS key AKIAYVP4CIPPERUVIFXG in commit fbc14303, file keys, line 4
    In the test: Nothing. The current test_keys repo returns other verified results (an AWS canary key in new_key and a URI in keys)
  • README: trufflehog git https://github.com/trufflesecurity/test_keys --results=verified
    In the test: Network access to GitHub and AWS. Cloning and verifying both need it, so this check cannot pass on an offline rerun

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.