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

kp3

v0.1.0

Published

Kill the process bound to a TCP port from the command line

Readme

kp

kp is a tiny cross-platform CLI that finds the process bound to a TCP port and sends it a signal. Install it globally via npm or Homebrew and terminate a port hog with a single command.

Install

# npm (global)
npm install -g kp3

# Homebrew
brew tap aboutmydreams/kp
brew install kp

The npm package name is kp3. Once you secure the unscoped kp name on npm you can rename the package and update these commands.

Usage

kp <port> [options]

| Option | Description | | --- | --- | | -f, --force | Send SIGKILL instead of SIGTERM | | --signal=<name> | Send an explicit signal (overrides --force) | | -h, --help | Show the inline help |

Examples:

kp 5173             # send SIGTERM (default) to any PID on TCP port 5173
kp 8080 --force     # force kill
kp 3000 --signal=SIGINT

When no processes are bound to the port you will see No process found listening on TCP port <port>.

Requirements

  • Node.js 14 or newer (used for the CLI runtime)
  • One of lsof, fuser, ss, or netstat must be available on the host (macOS and most Linux distributions ship with at least one of these)

Local development

npm install
npm link  # exposes `kp` in your PATH while developing

You can test the CLI directly:

kp 3000
kp 8080 --force
kp 5000 --signal=SIGINT

Release workflow (npm + Homebrew)

  1. Update package.json with the new version (npm version <patch|minor|major>).
  2. Commit the changes and tag the release: git commit -am "Release vX.Y.Z" && git tag vX.Y.Z.
  3. Publish to npm: npm publish --access public.
  4. Push the branch and tag: git push origin main --tags.
  5. Create a GitHub release from tag vX.Y.Z and attach the source tarball (or rely on the auto-generated archive).
  6. In homebrew-kp/Formula/kp.rb, update url if the version changed and replace sha256 with the checksum of the new archive:
    curl -L -o kp.tar.gz https://github.com/aboutmydreams/kp/archive/refs/tags/vX.Y.Z.tar.gz
    shasum -a 256 kp.tar.gz
  7. Commit and push the updated formula to aboutmydreams/homebrew-kp, then tag it if desired.

Once these steps are complete, users can upgrade via either npm or Homebrew.

License

MIT