pickfit

BrowseDeveloper CLIs

dive

Tool for exploring Docker image layers and finding ways to shrink size.

Tested on LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

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

  • go:github.com/go-jose/go-jose/v4 v4.1.5 Go JOSE: DoS when parsing JWKs that contain RSA keys (GHSA-mgcc-cww5-fp2q, high, fixed in 4.1.6)

Linux x86_64

  1. Download dive v0.13.1 linux_amd64 tarball from GitHub releases and install to ~/.local/bin

    DIVE_VERSION=0.13.1
    curl -fL "https://github.com/wagoodman/dive/releases/download/v${DIVE_VERSION}/dive_${DIVE_VERSION}_linux_amd64.tar.gz" -o /tmp/dive.tar.gz
    mkdir -p ~/.local/bin
    tar -xzf /tmp/dive.tar.gz -C /tmp && mv /tmp/dive ~/.local/bin/dive && chmod +x ~/.local/bin/dive && ~/.local/bin/dive --version

Check that it works

dive --version

The output should contain “dive 0.13.1”.

First thing to try

cat > /tmp/make_archive.py <<'PYEOF'
import tarfile, json, os, io, tempfile, hashlib

tmpdir = "/tmp/dive-image"
os.makedirs(tmpdir, exist_ok=True)

# Create two layers to test layer diff
# Layer 1: contains /hello.txt
# Layer 2: adds /world.txt and modifies /hello.txt

def make_layer_tar(files, path):
    buf = io.BytesIO()
    with tarfile.open(fileobj=buf, mode='w') as tf:
        for name, content in files.items():
            data = content.encode()
            ti = tarfile.TarInfo(name=name)
            ti.size = len(data)
            ti.mtime = 0
            tf.addfile(ti, io.BytesIO(data))
    data = buf.getvalue()
    with open(path, 'wb') as f:
        f.write(data)
    return hashlib.sha256(data).hexdigest()

layer1_hash = make_layer_tar({"hello.txt": "hello from layer1\n"}, "/tmp/dive-image/layer1.tar")
layer2_hash = make_layer_tar({"world.txt": "hello world\n", "hello.txt": "modified hello\n"}, "/tmp/dive-image/layer2.tar")

# Create config json
config = {
    "architecture": "amd64",
    "os": "linux",
    "rootfs": {"type": "layers", "diff_ids": [f"sha256:{layer1_hash}", f"sha256:{layer2_hash}"]},
    "history": [{"created": "2025-01-01T00:00:00Z"}, {"created": "2025-01-02T00:00:00Z"}],
    "config": {}
}
import hashlib as hl
config_data = json.dumps(config).encode()
config_hash = hl.sha256(config_data).hexdigest()

with open(f"/tmp/dive-image/{config_hash}.json", "wb") as f:
    f.write(config_data)

# manifest.json
manifest = [{
    "Config": f"{config_hash}.json",
    "RepoTags": ["test:latest"],
    "Layers": ["layer1.tar", "layer2.tar"]
}]
with open("/tmp/dive-image/manifest.json", "w") as f:
    json.dump(manifest, f)

with open("/tmp/dive-image/repositories", "w") as f:
    json.dump({"test": {"latest": "layer2"}}, f)

# Create docker save tarball
with tarfile.open("/tmp/test-image.tar", "w") as out:
    for fname in ["manifest.json", "repositories", f"{config_hash}.json", "layer1.tar", "layer2.tar"]:
        out.add(f"/tmp/dive-image/{fname}", arcname=fname)

print(f"Created /tmp/test-image.tar with layers {layer1_hash[:12]}, {layer2_hash[:12]}, config {config_hash[:12]}")
print(f"Size: {os.path.getsize('/tmp/test-image.tar')}")

PYEOF
python3 /tmp/make_archive.py
tar -tvf /tmp/test-image.tar
dive --source docker-archive /tmp/test-image.tar --json /tmp/dive-output.json

What it does

  • Indicate what changed in each layer
    Tested
  • Estimate image efficiency and wasted space
    Tested
  • Show Docker image contents by layer
    Not shown working
  • Build image and analyze immediately
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • explore Docker image contents broken down by layer
  • estimate image efficiency and wasted space

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 4 Nov 2026
  • Version 0.13.1

Differences the test machine hit

  • README: Install via go install or pacman -S dive (and brew/docker)
    In the test: On Debian without Go/Docker, downloaded prebuilt linux_amd64 tarball from GitHub releases and extracted to ~/.local/bin
  • README: dive nginx:latest uses Docker daemon by default
    In the test: Used --source docker-archive with a crafted docker save tarball to test without Docker daemon; registry source not available in v0.13.1
  • README: dive build builds via Docker
    In the test: dive build requires docker client executable; fails gracefully when absent

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.