pickfit

BrowseSecurity & networking tools

SOPS

Editor for encrypted YAML, JSON, ENV, INI and binary files using AWS KMS, GCP KMS, Azure Key Vault, HuaweiCloud KMS, age or PGP.

Tested on Linux

Use it

Linux x86_64

  1. download sops v3.13.3 linux amd64 binary to ~/.local/bin and chmod +x

    mkdir -p ~/.local/bin && curl -fL -o ~/.local/bin/sops https://github.com/getsops/sops/releases/download/v3.13.3/sops-v3.13.3.linux.amd64 && chmod +x ~/.local/bin/sops
  2. download age v1.2.1 and generate an age key for the tests

    curl -fL -o /tmp/age.tar.gz https://github.com/FiloSottile/age/releases/download/v1.2.1/age-v1.2.1-linux-amd64.tar.gz && tar -xzf /tmp/age.tar.gz -C /tmp && cp /tmp/age/age /tmp/age/age-keygen ~/.local/bin/ && age-keygen -o ~/age-key.txt

Check that it works

sops --version --disable-version-check

The output should contain “sops 3.13.3”.

First thing to try

cat > secrets.yaml <<'EOF'
db_user: admin
db_password: hunter2
EOF
cat > secrets.env <<'EOF'
API_TOKEN=s3cr3tvalue
EOF
sops encrypt --age "$(age-keygen -y ~/age-key.txt)" secrets.yaml > secrets.enc.yaml && cat secrets.enc.yaml && SOPS_AGE_KEY_FILE=~/age-key.txt sops decrypt secrets.enc.yaml

Run sops encrypt --age <age public key> <file> > <encrypted file> to encrypt your first secrets file.

What it does

  • Edit encrypted YAML, JSON, ENV, INI and binary files
    How to use it
    1. Encrypt a file with sops encrypt --age <age public key> <file> > <encrypted file>.
    2. Open it for editing with SOPS_AGE_KEY_FILE=<key file> sops edit <encrypted file>; it is re-encrypted when you save.
    3. View the plain contents with SOPS_AGE_KEY_FILE=<key file> sops decrypt <encrypted file>.
    Tested
  • Encrypt with cloud KMS, age or PGP keys
    How to use it
    1. Encrypt with an age key using sops encrypt --age <age public key> <file> > <encrypted file>.
    2. Decrypt with SOPS_AGE_KEY_FILE=<key file> sops decrypt <encrypted file>.
    Tested

How far pickfit got

Linux x86_64

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

Good for

  • edit encrypted YAML or JSON secret files

An alternative to hiera-eyaml and credstash.

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 sops 3.13.3

Differences the test machine hit

  • README: mv sops-v3.13.3.linux.amd64 /usr/local/bin/sops
    In the test: Without root I saved the binary to ~/.local/bin/sops, which is on PATH.
  • README: encrypts with ... age
    In the test: SOPS does not make age keys itself. I downloaded the separate age release to run age-keygen.
  • README: (no mention)
    In the test: `sops edit` exits 200 with 'File has not changed, exiting.' if the editor makes no changes (cmd 6).

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.