pickfit

BrowseDeveloper CLIs

StackEngine CLI

Local CLI that redacts secrets into tokens before LLM exposure and restores them afterward.

Tested on macOS and Linux

Use it

macOS arm64

  1. npm install -g stackengine

    npm install -g stackengine

Check that it works

stackengine --version && which stackengine && stackengine --help

The output should contain “stackengine v1.0.6”.

First thing to try

echo -n "api_key: sk-proj-abc123secretkeyXYZ" | pbcopy
pbpaste | cat -A
stackengine copy 2>&1
pbpaste 2>&1

Run stackengine copy to redact secrets in your clipboard.

Linux x86_64

  1. install stackengine globally via npm

    npm install -g stackengine

Check that it works

stackengine --version

The output should contain “stackengine v1.0.6”.

First thing to try

cat > /tmp/prod.yaml <<'YAML'
apiVersion: v1
kind: Secret
metadata:
  name: test-secret
  namespace: prod
data:
  # database uri with password
  db_uri: "postgres://user:MySup3rDBPassword!@db.example.com:5432/mydb"
  api_key: "AKIAIOSFODNN7EXAMPLE"
  # PEM block
  private_key: |
    -----BEGIN RSA PRIVATE KEY-----
    MIIEowIBAAKCAQEA7b...
    -----END RSA PRIVATE KEY-----
YAML
cat /tmp/prod.yaml
stackengine redact /tmp/prod.yaml -o /tmp/prod.redacted.yaml && echo "EXIT:$?" && ls -lh /tmp/prod.redacted.yaml .stackengine/vault.lock && cat /tmp/prod.redacted.yaml

Run stackengine copy to redact secrets in your clipboard.

What it does

  • Redact secrets in your clipboard in place
    How to use it
    1. Copy text that contains a secret to the clipboard.
    2. Run stackengine copy to replace the secrets in the clipboard with tokens.
    3. Paste as usual to use the redacted text.
    Tested
  • Redact secrets in a file
    Not tested
  • Restore secrets from a saved token map
    Not tested
  • Start a local proxy that redacts secrets
    Not shown working

How far pickfit got

macOS arm64

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

Linux x86_64

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

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

Good for

  • redact secrets in a configuration file
  • restore secrets from LLM response
  • block git commits containing hardcoded credentials
  • proxy LLM API traffic for real-time redaction
  • scan a file for secrets without modifying it

An alternative to Gitleaks / TruffleHog and Detect-Secrets.

How pickfit tested it

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

macOS arm64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 1.0.6

Differences the test machine hit

  • README: brew tap gweisec/stackengine / brew install stackengine
    In the test: npm install -g stackengine works; brew not tested but npm is recommended and succeeded

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 1.0.6

Differences the test machine hit

  • README: stackengine copy reads clipboard
    In the test: headless Linux has no display; tool exits 1 with 'Cannot access system clipboard (timeout or no GUI display found)'

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.