pickfit

BrowseDeveloper CLIs

patient-zero

Scans lockfiles, processes, MCP configs and persistence for known npm/PyPI supply-chain IoCs.

Tested on macOS and Linux

Use it

macOS arm64

  1. install via npx and check version

    npx -y patient-zero@latest --version

Check that it works

npx -y patient-zero@latest --version

The output should contain “0.2.1”.

First thing to try

mkdir -p /tmp/pz-triage && cd /tmp/pz-triage && npx -y patient-zero@latest 2>&1

Run npx patient-zero@latest to scan the current machine for known supply-chain IoCs.

Linux x86_64

  1. install patient-zero globally via npm

    npm install -g patient-zero@latest

Check that it works

npm install -g patient-zero@latest && patient-zero --version && which patient-zero

The output should contain “0.2.1”.

First thing to try

patient-zero scan --no-github --offline --sarif /tmp/patient-zero.sarif 2>&1

Run npx patient-zero@latest to scan the current machine for known supply-chain IoCs.

What it does

  • Check your machine for supply-chain exposure quickly
    How to use it
    1. Run npx patient-zero@latest.
    2. Read the result; it reports either matched IoCs or "No known IoCs matched."
    Tested
  • Block malicious installs before postinstall runs
    Not shown working
  • Scan every commit in CI
    Not shown working

How far pickfit got

macOS arm64

  1. Installs
  2. Starts
  3. 1 of 3 features work
  4. Needs the network

Linux x86_64

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

Good for

  • block malicious installs before postinstall runs
  • triage machine for supply-chain IoCs in 30 seconds
  • populate GitHub Security tab with SARIF findings in CI

An alternative to Socket, Snyk Open Source and osv-scanner.

How pickfit tested it

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

macOS arm64

Its main function works

  • Replayed from scratch
  • Needed the network
  • Checked on 30 Oct 2026
  • Version 0.2.1

Differences the test machine hit

  • README: npx patient-zero@latest
    In the test: add -y to npx for non-interactive box: npx -y patient-zero@latest
  • README: README example shows chalk@4.0.0 flagged CRITICAL and install mode blocks malicious installs
    In the test: bundled data/iocs.json has 0 package indicators (only file/process/github/mcp), so chalk@4.0.0 install passes through instead of blocking

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.2.1

Differences the test machine hit

  • README: npx patient-zero@latest
    In the test: global install with npm install -g patient-zero@latest puts patient-zero on PATH; README npx form also works and was verified

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.