pickfit

BrowseDeveloper CLIs

proc

Semantic CLI tool to manage processes by port, PID, name, or path.

Tested on Linux

Use it

Linux x86_64

  1. install proc via npm

    npm install -g proc-cli
  2. first run downloads verified binary

    proc --version

Check that it works

proc --version

The output should contain “proc”.

First thing to try

python3 -m http.server 3000
proc on :3000

Run proc on :<port> to see which process is using a port.

What it does

  • Find which process is using a port
    How to use it
    1. Run proc on :<port> to see the process using that port.
    Tested
  • Kill processes by port, name, or other targets
    How to use it
    1. Run proc kill :<port> :<port> <name> --yes to kill all matching processes at once.
    Tested
  • See why a port is busy and trace its process ancestry
    How to use it
    1. Run proc why :<port> to show the process using the port and its parent chain.
    Tested
  • Watch processes in real time
    How to use it
    1. Run proc watch -n 1 to refresh the process list every second.
    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 what process is using port 3000
  • kill process using port 3000
  • find processes running a program file
  • list node processes in current directory
  • free a busy port and verify it is free

An alternative to lsof.

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 30 Oct 2026
  • Version 2.0.2

Differences the test machine hit

  • README: npm install -g proc-cli
    In the test: first proc invocation downloads the Linux binary to ~/.local/lib/node_modules/proc-cli/proc and verifies checksum (requires network)
  • README: proc kill :3000 :8080 node
    In the test: append --yes (proc kill :3000 :8080 node --yes) when stdin is not a terminal, otherwise exit 4 needs_confirmation and nothing is killed

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.