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

pscout

v1.0.0

Published

CLI dev server visibility tool — see what's running on your ports

Readme

pscout

See what's running on your ports.

Developers running multiple local servers have no clean way to see what's listening, on which port, and whether it's intentional or orphaned. lsof and netstat output is unreadable. pscout fixes that.

Install

npm install -g pscout

Usage

pscout              # one-shot table view
pscout watch        # live refresh every 2s
pscout kill <port>  # kill process on a port (with confirmation)
pscout --all        # include system ports in output
pscout --simple     # ASCII borders (auto-enabled in tmux)
pscout --unicode    # force unicode (override tmux detection)

Output

  ╭────────────────────────────────────────────────────────────╮
  │  pscout  ·  10 ports  ·  11:42:03 AM                    │
  ╰────────────────────────────────────────────────────────────╯

  DEV SERVERS
  ●  :3100   node      PID 15710   2h 14m   next dev · ~/projects/foo
  ●  :3200   node      PID 71202   0h 08m   vite · ~/projects/bar
  ●  :8080   node      PID 35041   4h 01m   node server.js · ~/projects/baz
  ●  :3335   Python    PID 62684   1h 22m   uvicorn main:app · ~/projects/api

  INFRASTRUCTURE
  ◆  :6379   Redis     PID 784     8h 30m
  ◆  :5432   Postgres  PID 796     8h 30m
  ◆  :11434  Ollama    PID 1782    5h 10m

  7 system ports hidden · run --all to show

Kill flow

$ pscout kill 8082

  Kill process on :8082?
  node · PID 18242 · running 3h 55m · node server.js · ~/projects/baz

  [y/N] y
  sending SIGTERM to PID 18242...
  killed.

Sends SIGTERM first. If the process doesn't exit within 1 second, follows up with SIGKILL.

Categorization

| Category | Rule | |---|---| | Dev server | node or Python process on port > 1024, not known infra | | Infrastructure | redis-server, postgres, mysql, mongod, ollama | | System | Everything else (hidden by default) |

Flags

| Flag | Description | |---|---| | --all | Show system ports | | --simple | ASCII borders (auto in tmux) | | --unicode | Force unicode borders | | --help | Show help | | --version | Show version |

Requirements

  • macOS (uses lsof)
  • Node.js >= 18

License

MIT