pickfit

BrowseData & database tools

gron

Command-line tool that transforms JSON into discrete assignments so it can be searched with grep, and converts them back into JSON.

Tested on Linux

Use it

Linux x86_64

  1. Download gron v0.7.1 linux-amd64 release tarball, extract, move binary to ~/.local/bin

    cd /tmp && curl -fsSLO https://github.com/tomnomnom/gron/releases/download/v0.7.1/gron-linux-amd64-0.7.1.tgz && tar xzf gron-linux-amd64-0.7.1.tgz && mkdir -p ~/.local/bin && mv gron ~/.local/bin/
Where the README and reality differ
  • README: tar xzf gron-linux-amd64-0.1.5.tgz
    What worked: The current release is v0.7.1; download gron-linux-amd64-0.7.1.tgz from the GitHub releases page

Check that it works

gron --help

The output should contain “Transform JSON (from a file, URL, or stdin) into discrete assignments to make it greppable”.

First thing to try

mkdir -p testdata && cat > testdata/two.json <<'EOF'
{"name":"Tom","github":"https://github.com/tomnomnom/","likes":["code","cheese","meat"],"contact":{"email":"mail@tomnomnom.com","twitter":"@TomNomNom"}}
EOF
gron testdata/two.json

Run gron <file> on a JSON file to see its contents as one assignment per line.

What it does

  • Flatten JSON into lines you can grep
    How to use it
    1. Run gron <file> to print each value as an assignment such as json.contact.twitter = "...";.
    2. Pipe the output to grep to find the path to a value.
    Tested
  • Turn filtered assignments back into JSON
    How to use it
    1. Run gron <file> | grep <pattern> | grep -v <pattern> | gron --ungron to keep only the lines you want and rebuild them as JSON.
    Tested
  • Read JSON from a file, URL, or standard input
    How to use it
    1. Pass a file directly with gron <file>.
    2. Or pipe JSON in with cat <file> | gron.
    Tested
  • Output gron data as a JSON stream
    Not shown working

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

  • explore large JSON API responses with poor documentation
  • diff two JSON files
  • find the path to a value in deeply nested JSON

An alternative to jq.

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

Differences the test machine hit

  • README: sudo mv gron /usr/local/bin/
    In the test: mv gron ~/.local/bin/ (no root in this box)
  • README: gron testdata/two.json
    In the test: testdata/two.json is in the repository but does not come with the binary; it was recreated by hand

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.