pickfit

BrowseDeveloper CLIs

dandavison/delta

Syntax-highlighting pager for git, diff, grep, and blame output.

Use it

Before you install: known vulnerabilities

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

  • crates:quick-xml 0.32.0 Quadratic run time when checking a start tag for duplicate attribute names (RUSTSEC-2026-0194, high, fixed in 0.41.0)
See 1 more

Linux x86_64

  1. download delta-0.20.1 tarball from github releases

    curl -fsSL -L -o /tmp/delta.tar.gz https://github.com/dandavison/delta/releases/download/0.20.1/delta-0.20.1-x86_64-unknown-linux-gnu.tar.gz
  2. extract and install delta binary to ~/.local/bin

    mkdir -p ~/.local/bin && tar xzf /tmp/delta.tar.gz -C /tmp && cp /tmp/delta-0.20.1-x86_64-unknown-linux-gnu/delta ~/.local/bin/delta && chmod +x ~/.local/bin/delta
Where the README and reality differ
  • README: delta --show-syntax-themes --dark runs standalone
    What worked: requires piped diff input (e.g. cat sample.diff | delta --show-syntax-themes); without stdin it hangs waiting for input, and --paging=never avoids pager hang

Check that it works

delta --version

The output should contain “delta 0.20.1”.

First thing to try

cat > /tmp/sample.diff <<'EOF'
diff --git a/example.py b/example.py
index 1111111..2222222 100644
--- a/example.py
+++ b/example.py
@@ -1,5 +1,5 @@
 def hello(name):
-    print("hello " + name)
+    print(f"hello {name}")
     return 42

 if __name__ == "__main__":
EOF
cat /tmp/sample.diff
echo "---sample ready---"
cat /tmp/sample.diff | delta --show-syntax-themes > /tmp/themes2.txt 2>&1; echo done; wc -l /tmp/themes2.txt; head -n 5 /tmp/themes2.txt

What it does

  • View diffs side-by-side with wrapping
    Tested
  • Show line numbers in diffs
    Tested
  • Syntax highlight diffs by language
    Not shown working
  • Highlight word-level changes in diffs
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

An alternative to diff-highlight and diff-so-fancy.

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.20.1

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.