pickfit

BrowseOther

Stats

Menu bar app that monitors macOS system resources.

Tested on macOS

Use it

macOS arm64

  1. Install Stats cask to user Applications

    mkdir -p ~/Applications && brew install --cask --appdir=$HOME/Applications stats

First thing to try

open ~/Applications/Stats.app

What it does

  • Monitor memory usage
    Tested
  • Monitor CPU utilization
    Not tested
  • Monitor network usage
    Not shown working
  • View temperature voltage power sensors
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Opens to its setup screen
  3. 1 of 4 features work
  4. Works offline

Good for

  • monitor CPU utilization
  • monitor memory usage
  • monitor network usage
  • check battery level
  • show multiple time zone clocks

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

A feature worked when operated

  • Replayed from scratch
  • Checked on 4 Nov 2026
  • Version 3.0.25

When pickfit opened it, its first-run (setup) screen rendered. pickfit then used it, and this worked: monitor memory usage. The launch passed again with the network off.

Differences the test machine hit

  • README: brew install stats
    In the test: brew install --cask --appdir=$HOME/Applications stats (default writes /Applications and asks for sudo password)

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.