Petri Labs

local development / Node.js CLI

portscan-dev

See which development processes own local ports and stop them deliberately.

portscan-dev lists listeners on common development and service ports with their process, PID, uptime, and command. It can also send a selected signal to the process holding one or more explicitly named ports.

npm packageSource on GitHub

Installation

npx @barissozudogru/portscan-dev

Platform requirements and configuration are documented in the repository instructions.

Capabilities

  • Scan a configurable development-port range
  • Recognize common database, queue, model, and Docker service ports
  • Show PID, process, uptime, and command details
  • Return JSON or stop explicitly selected listeners

Use cases

  • Finding the process behind an address-already-in-use error
  • Cleaning up forgotten local development servers
  • Feeding local listener data into a script or diagnostic workflow

Evidence

verified live listener

A temporary Python server is resolved to the process holding port 4567.

The scan ran against a real local listener started for verification, then the process was stopped. No network range was probed.

port     4567
process  Python
uptime   00:01
scope    local listener
Inspect the source

Limitations

  • Designed for macOS and Linux process tooling
  • Stopping a process is opt-in and should be used only after reviewing its identity
  • It is a local developer utility, not a network security scanner
Full directory