pickfit

BrowseInfra & DevOps tools

Dust

A command-line disk usage tool, like du, that shows which directories and files use the most disk space with percentage bars.

Tested on Linux

Use it

Linux x86_64

  1. Download install.sh

    curl -sSfL -o /tmp/dust-install.sh https://raw.githubusercontent.com/bootandy/dust/refs/heads/master/install.sh
  2. Run installer (installs dust v1.2.7 musl binary to ~/.local/bin)

    sh /tmp/dust-install.sh

Check that it works

dust --version

The output should contain “Dust 1.2.7”.

First thing to try

mkdir -p /tmp/sample/src/utils /tmp/sample/docs /tmp/sample/media && head -c 300000 /dev/urandom > /tmp/sample/media/big.png && head -c 120000 /dev/urandom > /tmp/sample/src/main.rs && head -c 40000 /dev/urandom > /tmp/sample/src/utils/helper.rs && head -c 60000 /dev/urandom > /tmp/sample/docs/guide.md && head -c 5000 /dev/urandom > /tmp/sample/docs/notes.txt
cd /tmp/sample && dust -n 10

Run dust inside a directory to see which subdirectories and files use the most space.

What it does

  • List the biggest subdirectories with percentage bars
    How to use it
    1. Go to the directory you want to check with cd <directory>.
    2. Run dust -n 10 to show the 10 largest entries with percentage bars.
    Tested
  • Show only the largest files
    How to use it
    1. Run dust -F <directory> to list only files, largest first.
    Tested
  • Group disk usage by file type
    How to use it
    1. Run dust -t <directory> to see space used per file extension.
    Tested
  • Output directory sizes as JSON
    How to use it
    1. Run dust -j <directory> to print sizes as nested JSON.
    Tested

How far pickfit got

Linux x86_64

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

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

Good for

  • find the largest files on disk
  • see which directories use the most disk space
  • export directory sizes as JSON

An alternative to du, ncdu, dua and dutree.

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 Dust 1.2.7

Differences the test machine hit

  • README: curl -sSfL .../install.sh | sh
    In the test: Works, but the script uses bash 'echo -e' with a bash shebang; under sh (dash) every message is prefixed with a literal '-e'. Purely cosmetic.
  • README: curl ... | sh
    In the test: The script downloads a prebuilt release binary from GitHub (it cannot be read as a script) and, with no writable /usr/local/bin, installs to ~/.local/bin

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.