pickfit

BrowseSecurity & networking tools

gping

Terminal tool that pings one or more hosts, or times commands, and draws the results as a live graph.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: rustc>=1.67.0 (for cargo install)
  • Needs the network
  1. Download the gping-v1.21.0 Linux musl x86_64 release tarball and install the binary to ~/.local/bin

    mkdir -p ~/.local/bin /tmp/gp && curl -fsSL -o /tmp/gp/gping.tar.gz https://github.com/orf/gping/releases/download/gping-v1.21.0/gping-Linux-musl-x86_64.tar.gz && tar -xzf /tmp/gp/gping.tar.gz -C /tmp/gp && install -m 755 /tmp/gp/gping ~/.local/bin/gping

Check that it works

gping --help

The output should contain “Ping, but with a graph.”.

First thing to try

sleep 5 | script -qfec "stty cols 100 rows 25; timeout -s INT 3 gping --tcp --tcp-port 9 127.0.0.1 localhost" /tmp/f1b.log >/dev/null; grep -a -o -E '(127\.0\.0\.1|localhost)[^[]{0,40}|[0-9]+\.[0-9]+ms' /tmp/f1b.log

Run gping <host> in a terminal to start a live ping graph for a host; press Ctrl+C to quit.

What it does

  • Graph ping times for several hosts at once
    How to use it
    1. Run gping --tcp --tcp-port <port> <host1> <host2> to ping several hosts over TCP and watch them on one graph.
    2. Read each host's latest and minimum ping time in the legend.
    3. Press Ctrl+C to stop.
    Tested
  • Choose your own graph colours
    How to use it
    1. Run gping --cmd -c '<colour1>,<colour2>' '<command1>' '<command2>' with hex colours such as #ff0000.
    2. Each line on the graph uses the colour given in the same order.
    Tested
  • Graph how long commands take to run
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • compare ping latency of multiple hosts in a terminal graph
  • graph execution time of commands like curl
  • ping AWS cloud regions by shorthand

An alternative to ping.

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: cargo install gping / pacman / apk / apt install gping
    In the test: The box has no Rust toolchain and no root, so I used the prebuilt gping-Linux-musl-x86_64.tar.gz from GitHub releases (the README mentions the MUSL build for distributions with an old glibc)
  • README: Just run `gping [host]` (ICMP ping)
    In the test: The box has no system `ping` binary, which gping calls for ICMP. To check several hosts I used `--tcp --tcp-port 9` against local addresses, where a refused connection counts as a pong.
  • README: gping is used interactively in a terminal
    In the test: gping is a full-screen terminal app and needs a terminal. Without one it drew nothing to stdout, so I ran it under `script` with `timeout -s INT` and searched the recorded output with grep.

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.