pickfit

BrowseData & database tools

jless

A terminal JSON viewer for reading, exploring and searching JSON data with collapsible structure and vim-style navigation.

Use it

Before you install: known vulnerabilities

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

  • crates:xcb 0.8.2 Out of bounds read in xcb (GHSA-2xpg-3hx4-fm9r, critical, fixed in 1.0.0)
  • crates:nix 0.22.1 Out-of-bounds write in nix::unistd::getgrouplist (GHSA-wgrg-5h56-jg27, high, fixed in 0.22.2)

Linux x86_64

  1. Download and unzip the v0.9.0 x86_64 Linux release binary

    mkdir -p ~/.local/bin /tmp/jl && curl -fsSL -o /tmp/jl/jless.zip https://github.com/PaulJuliusMartinez/jless/releases/download/v0.9.0/jless-v0.9.0-x86_64-unknown-linux-gnu.zip && unzip -o /tmp/jl/jless.zip -d ~/.local/bin && chmod +x ~/.local/bin/jless
  2. Download libxcb1, libxau6 and libxdmcp6 debs from the Debian pool and unpack them into ~/.local/xcb

    cd /tmp/jl && curl -fsSLO http://deb.debian.org/debian/pool/main/libx/libxcb/libxcb1_1.15-1_amd64.deb && curl -fsSLO http://deb.debian.org/debian/pool/main/libx/libxau/libxau6_1.0.9-1_amd64.deb && curl -fsSLO http://deb.debian.org/debian/pool/main/libx/libxdmcp/libxdmcp6_1.1.2-3_amd64.deb && mkdir -p ~/.local/xcb && dpkg -x libxcb1_1.15-1_amd64.deb ~/.local/xcb && dpkg -x libxau6_1.0.9-1_amd64.deb ~/.local/xcb && dpkg -x libxdmcp6_1.1.2-3_amd64.deb ~/.local/xcb
  3. Put the binary in ~/.local/xcb and add a wrapper in ~/.local/bin that sets LD_LIBRARY_PATH

    unzip -o /tmp/jl/jless.zip -d ~/.local/xcb && printf '#!/bin/sh\nLD_LIBRARY_PATH="$HOME/.local/xcb/usr/lib/x86_64-linux-gnu${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" exec "$HOME/.local/xcb/jless" "$@"\n' > ~/.local/bin/jless && chmod +x ~/.local/bin/jless ~/.local/xcb/jless
  4. Unpack libxcb-render0, libxcb-shape0 and libxcb-xfixes0, then confirm jless --version

    cd /tmp/jl && B=http://deb.debian.org/debian/pool/main/libx/libxcb && curl -fsSLO $B/libxcb-render0_1.15-1_amd64.deb && curl -fsSLO $B/libxcb-shape0_1.15-1_amd64.deb && curl -fsSLO $B/libxcb-xfixes0_1.15-1_amd64.deb && dpkg -x libxcb-render0_1.15-1_amd64.deb ~/.local/xcb && dpkg -x libxcb-shape0_1.15-1_amd64.deb ~/.local/xcb && dpkg -x libxcb-xfixes0_1.15-1_amd64.deb ~/.local/xcb && jless --version
Where the README and reality differ
  • README: The release binary is presented as a single standalone binary; X11 libraries are mentioned only for building from source
    What worked: The prebuilt Linux binary is dynamically linked against libxcb.so.1, libxcb-render.so.0, libxcb-shape.so.0 and libxcb-xfixes.so.0 and fails to start without them (libxcb1, libxcb-render0, libxcb-shape0, libxcb-xfixes0 runtime packages)

Check that it works

cd /tmp/jl && B=http://deb.debian.org/debian/pool/main/libx/libxcb && curl -fsSLO $B/libxcb-render0_1.15-1_amd64.deb && curl -fsSLO $B/libxcb-shape0_1.15-1_amd64.deb && curl -fsSLO $B/libxcb-xfixes0_1.15-1_amd64.deb && dpkg -x libxcb-render0_1.15-1_amd64.deb ~/.local/xcb && dpkg -x libxcb-shape0_1.15-1_amd64.deb ~/.local/xcb && dpkg -x libxcb-xfixes0_1.15-1_amd64.deb ~/.local/xcb && jless --version

The output should contain “jless 0.9.0”.

First thing to try

cd ~/work && cat > sample.json <<'EOF'
{"name": "jules", "kind": "jellyfish", "tags": ["mascot", "logo"], "stats": {"arms": 8, "alive": true}, "note": "found in the deep sea"}
EOF
cat > drive.py <<'EOF'
import os, pty, sys, time, re, select, struct, fcntl, termios
f = sys.argv[1]; keys = sys.argv[2:]
pid, fd = pty.fork()
if pid == 0:
    os.environ['TERM'] = 'xterm-256color'
    os.execvp('jless', ['jless', f])
fcntl.ioctl(fd, termios.TIOCSWINSZ, struct.pack('HHHH', 24, 80, 0, 0))
def read(t=1.0):
    out = b''; end = time.time() + t
    while time.time() < end:
        r, _, _ = select.select([fd], [], [], 0.1)
        if r:
            try: d = os.read(fd, 65536)
            except OSError: break
            if not d: break
            out += d
    return out.decode('utf-8', 'replace')
def show(label, s):
    colors = len(re.findall(r'\x1b\[[0-9;]*3[0-9;]*m', s))
    txt = re.sub(r'\x1b\[[0-9;?]*[A-Za-z]', ' ', s)
    txt = re.sub(r'\x1b[()][A-Z0-9]|\x1b[=>]', '', txt)
    txt = re.sub(r'[ \t]+', ' ', txt)
    print('=== %s (color escapes: %d) ===' % (label, colors))
    print(txt.strip())
show('initial', read(1.5))
for k in keys:
    k = k.encode().decode('unicode_escape')
    os.write(fd, k.encode()); show('after %r' % k, read(0.8))
os.write(fd, b'q'); read(0.8)
_, st = os.waitpid(pid, 0)
print('jless exit status:', os.waitstatus_to_exitcode(st))
sys.exit(os.waitstatus_to_exitcode(st))
EOF
cd ~/work && python3 drive.py sample.json

Run jless <file> to open a JSON file in the viewer, and press q to quit.

What it does

  • View JSON with syntax highlighting
    How to use it
    1. Run jless <file> to open a JSON file.
    2. Read the colored, line-numbered tree of keys and values.
    3. Press q to quit.
    Tested
  • Expand and collapse objects and arrays
    How to use it
    1. Open a file with jless <file>.
    2. Move to an object or array and press Space to collapse it into one line.
    3. Press Space again to expand it.
    Tested
  • Move around with vim-style keys
    How to use it
    1. Open a file with jless <file>.
    2. Press j to move down one line.
    3. Press G to jump to the last item; the status bar shows its path, such as .note.
    Tested
  • Search JSON with regular expressions
    How to use it
    1. Open a file with jless <file>.
    2. Type / followed by a regular expression and press Enter.
    3. Press n to go to the next match; the status bar shows the match count and path.
    Tested

How far pickfit got

Linux x86_64

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

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

Good for

  • view JSON files in the terminal
  • search JSON data with regular expressions

An alternative to less and 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
  • Version jless 0.9.0

Differences the test machine hit

  • README: Install via cargo install jless or OS package managers (pacman, xbps, pkgin, pkg)
    In the test: No Rust toolchain or root here, so I used the prebuilt release binary the README links from its releases page (v0.9.0 x86_64-unknown-linux-gnu zip)
  • README: sudo apt-get install the libxcb packages
    In the test: Without root: download the bookworm .debs from deb.debian.org, unpack them with dpkg -x into ~/.local/xcb, and run jless through a wrapper that sets LD_LIBRARY_PATH
  • README: jless is an interactive viewer
    In the test: It needs a TTY, so the checks drove it through a Python pty script (drive.py, setup command 7) that sends keystrokes and prints the screen with ANSI codes stripped. Typed-ahead input after '/' was dropped, so the keys must be sent separately

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.