npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

ferman

v0.1.10

Published

A CLI tool to inspect, diagnose, and manage local ports and processes with predictable output for humans and AI agents.

Downloads

981

Readme


⚡ What is ferman?

ferman is a CLI tool that tells you:

👉 what’s running on a port
👉 and frees it instantly

No guessing. No digging. No manual killing.


🚀 Quick Start

npx ferman 3000

That’s it.


🧠 What it does

  • finds the process using a port
  • shows what it is
  • lets you safely terminate it
  • works across macOS, Linux, and Windows
  • JSON and TOON output for automation and LLM workflows
  • listening port inventory
  • process targeting with --kill-all --name
  • includes an MCP wrapper for agent tool integration

🔥 Why use it?

Every dev hits this:

Error: port 3000 already in use

Instead of:

  • searching PID
  • running multiple commands
  • guessing processes

👉 just run:

npx ferman 3000

⚡ Common Usage

Inspect a port:

npx ferman 3000

Force kill:

npx ferman 3000 --force

Dry run:

npx ferman 3000 --dry

Multiple ports:

npx ferman 3000 5173 5432

List active listening ports:

npx ferman --list

List active Node.js processes:

npx ferman --node

Filter Node.js processes:

npx ferman --node --filter mcp

List active Node.js processes with listening ports:

npx ferman --node-ports

Kill all matching processes by pattern:

npx ferman --kill-all --name vite

🤖 For Scripts, CI & AI

Machine-readable output:

npx ferman 3000 --json

Listening ports inventory:

npx ferman --list --json

LLM-friendly structured output:

npx ferman 3000 --toon

Node.js processes with listening ports:

npx ferman --node-ports --json

Include the current ferman process in node listings:

npx ferman --node --self --json

Filter node-oriented listings:

npx ferman --node --filter mcp --json

Kill matching processes with a custom signal:

npx ferman --kill-all --name vite --signal SIGKILL --json

Plan mode (no kill, just recommendation):

npx ferman 3000 --plan --json

Watch mode:

npx ferman 3000 --watch --json

Watch mode, only on change:

npx ferman 3000 --watch --changed-only --json

MCP wrapper over stdio:

npx -p ferman ferman-mcp

Exposed MCP tools:

  • inspect_ports
  • release_ports
  • doctor_ports
  • list_node_processes
  • list_node_ports
  • get_output_schema

🧾 Example Output

JSON:

{
  "ok": true,
  "code": "PORT_RELEASED",
  "port": 3000,
  "busy": true,
  "action": "killed",
  "message": "Port released."
}

TOON:

ok: true
code: PORT_RELEASED
port: 3000
busy: true
processes[1]{pid,name}:
  1234,node
action: killed
message: Port released.

⚙️ Features

  • cross-platform (macOS, Linux, Windows)
  • safe process termination
  • port inspection and release
  • JSON and TOON output for automation and LLM workflows
  • listening port inventory
  • Node.js process and port visibility
  • process targeting by name or command pattern
  • optional self-inclusion for node-oriented diagnostics
  • configurable kill signals on Unix-like systems
  • multi-port support
  • plan & dry modes
  • watch mode
  • changed-only watch mode
  • MCP wrapper for agent tool integration
  • predictable exit codes
  • AI / agent-friendly output

📦 Install

npm install -g ferman

or just use:

npx ferman 3000

🧠 Philosophy

Dev tools should be fast, predictable, and boring.

ferman keeps local ports and processes observable and manageable
without friction.


❤️ Support

If this tool saves you time:

⭐ Star the repo
☕ Support via GitHub Sponsors

https://github.com/sponsors/borakilicoglu


🔗 Links

  • GitHub: https://github.com/borakilicoglu/ferman
  • npm: https://www.npmjs.com/package/ferman
  • Docs: https://borakilicoglu.github.io/ferman/