ptnix-cli 0.5.6

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 PTNIX Abhishek Verma
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,735 @@
+<p align="center">
+<p align="center">
+  <img width="220" height="220" alt="Ptnix" src="https://cdn.jsdelivr.net/gh/abhishekayu/ptnix@main/assets/logo.png" />
+</p>
+  <h1 align="center">Ptnix</h1>
+  <p align="center"><strong>Stop guessing what's running on your machine.</strong></p>
+  <p align="center">ptnix is a fast, cross-platform CLI to inspect ports, understand processes, and recover broken dev environments - built for real-world development workflows.</p>
+  <p align="center">
+    <a href="https://crates.io/crates/ptnix-cli"><img src="https://img.shields.io/crates/v/ptnix-cli.svg" alt="crates.io"></a>
+    <a href="https://www.npmjs.com/package/ptnix-cli"><img src="https://img.shields.io/npm/v/ptnix-cli.svg" alt="npm"></a>
+    <a href="https://github.com/abhishekayu/ptnix/releases"><img src="https://img.shields.io/github/v/release/abhishekayu/ptnix" alt="release"></a>
+    <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="license"></a>
+    <a href="https://marketplace.visualstudio.com/items?itemName=abhishekayu.ptnix"><img src="https://img.shields.io/visual-studio-marketplace/v/abhishekayu.ptnix?label=VS%20Code" alt="VS Code Marketplace"></a>
+  </p>
+</p>
+
+<br>
+
+```
+$ ptnix fix 3000
+
+  ⚡ Port 3000 in use
+  → Next.js (PID 81106) running for 7m 21s
+  → 🛡 safe to kill
+
+  • Sending SIGTERM to PID 81106
+  • Verified: PID 81106 has exited
+
+  ✔ Port 3000 is now free
+  Restart: npm run dev
+```
+
+<p align="center">
+  <b>Detects the process. Checks if it's safe. Kills it gracefully. Tells you how to restart.</b><br>
+  Try it now: <code>npx ptnix scan</code>
+</p>
+
+---
+
+## The Problem Every Developer Hits
+
+You've seen this before:
+
+```
+Error: listen EADDRINUSE: address already in use :::3000
+```
+
+A crashed dev server. A zombie process. Something unknown squatting on your port.
+
+So you do the ritual:
+
+```bash
+lsof -i :3000           # wall of text
+kill -9 <pid>            # hope it's not PostgreSQL
+# ...was that important?
+# how do I restart this thing?
+```
+
+This is fragile. It's blind. It tells you nothing about what you just killed.
+
+**ptnix replaces this entire workflow with one command.** A single CLI tool for port conflict resolution, process inspection, and dev server recovery.
+
+---
+
+## Instant Port Inspection
+
+```
+$ ptnix 3000
+
+  ⚡ Port 3000 in use
+  → Next.js (PID 81106)
+  → running for 7m 21s
+  → memory 42.9 MB
+  → detected Next.js (95% confidence)
+  → 🛡 safe to kill
+
+  📂 Detected project: Next.js
+  → dev command: npm run dev
+  → default port: 3000
+```
+
+ptnix tells you **what** is running, **whether it's safe** to kill, and **how to restart** it.
+
+---
+
+## Port Debugging: Before vs After
+
+| Task                       | Before                                      | After                      |
+| -------------------------- | ------------------------------------------- | -------------------------- |
+| Port 3000 stuck            | `lsof -i :3000 \| awk ... \| xargs kill -9` | `ptnix fix 3000`         |
+| "What's on my ports?"      | `lsof -iTCP -sTCP:LISTEN` (unreadable)      | `ptnix scan`             |
+| "Is this safe to kill?"    | Google the process name                     | ptnix tells you          |
+| "How do I restart?"        | Dig through package.json                    | ptnix shows the command  |
+| Zombie processes           | Hunt them one by one                        | `ptnix doctor -y`        |
+| Which port is my frontend? | Check config files                          | `ptnix group`            |
+| Start entire dev stack     | Open 5 terminals, run commands manually     | `ptnix up`               |
+| Stop everything            | Find and kill each process                  | `ptnix down`             |
+| "Is my port free?"         | `lsof -i :3000` and parse output            | `ptnix preflight 3000`   |
+| Monitor a flaky server     | Watch logs + manual restart                 | `ptnix watch 3000`       |
+| Duplicate port assignments | Manually diff config files                  | `ptnix registry check`   |
+| Run all checks in CI       | Write custom scripts                        | `ptnix ci`               |
+| Switch dev/staging config  | Edit .env files manually                    | `ptnix use staging`      |
+| Restart a crashed service  | Find port, kill, cd, re-run command         | `ptnix restart frontend` |
+| "Are my services running?" | Check each port manually                    | `ptnix status`           |
+| Stream logs from a port    | Figure out which container or log file      | `ptnix log 3000`         |
+
+---
+
+## Install
+
+> **Native binary. No Node. No runtime dependencies.** ~1.2MB, runs instantly.
+
+### One-line install (recommended)
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/abhishekayu/ptnix/main/install.sh | sh
+```
+
+### Package managers
+
+| Platform            | Command                                                                                          |
+| ------------------- | ------------------------------------------------------------------------------------------------ |
+| **Homebrew**        | `brew install abhishekayu/tap/ptnix`                                                           |
+| **Cargo**           | `cargo install ptnix-cli`                                                                      |
+| **npm**             | `npm install -g ptnix-cli`                                                                     |
+| **Scoop** (Windows) | `scoop bucket add ptnix https://github.com/abhishekayu/scoop-ptnix && scoop install ptnix` |
+| **Debian/Ubuntu**   | Download `.deb` from [releases](https://github.com/abhishekayu/ptnix/releases)                 |
+
+### Try instantly (no install)
+
+```bash
+npx ptnix scan
+```
+
+### Build from source
+
+```bash
+git clone https://github.com/abhishekayu/ptnix.git
+cd ptnix
+cargo install --path .
+```
+
+> **Supports** macOS (Intel + Apple Silicon), Linux (x86_64 + ARM64), and Windows.
+
+---
+
+## Usage Examples
+
+### Scan all listening ports
+
+```
+$ ptnix scan
+
+  ⚡ 5 active ports
+
+  PORT    PROCESS                PID      SERVICE        MEMORY     UPTIME     USER
+  ────────────────────────────────────────────────────────────────────────────────
+  3000    node                   81106    Next.js        42.9 MB    7m 17s     abhishek
+  3898    Code Helper (Plugin)   34290    Python         20.2 MB    3h 12m     abhishek
+  5237    Code Helper (Plugin)   34073    Python         20.1 MB    3h 12m     abhishek
+  5932    Code Helper (Plugin)   61773    Python         57.5 MB    58m 35s    abhishek
+  42050   OneDrive Sync Serv..   36643    Unknown        14.4 MB    3d 1h      abhishek
+```
+
+### Fix port conflicts and auto-restart
+
+```
+$ ptnix fix 3000 --run "npm run dev"
+
+  ✔ Killed safely  port 3000 is now free
+  🚀 Restarting: npm run dev
+```
+
+One command. Port cleared, dev server restarted.
+
+### Diagnose dev environment issues
+
+```
+$ ptnix doctor
+
+  🩺 2 issues found
+
+  1. Idle process Code Helper (PID 34290) at 0.0% CPU [auto-fixable]
+     → Idle Code Helper on port 3898 -- consider killing to free resources
+  2. Idle process Code Helper (PID 34073) at 0.0% CPU [auto-fixable]
+     → Idle Code Helper on port 5237 -- consider killing to free resources
+
+  ⚙ Run ptnix doctor -y to auto-fix 2 issues
+```
+
+### Group ports by service role
+
+```
+$ ptnix group --dev
+
+  ⚡ 4 active ports in 2 groups
+
+  ⚙ Frontend (2)
+  ────────────────────────────────────────────────────────────────────────────
+  3000    node                   81106    Next.js        42.9 MB    7m 21s     abhishek
+  3898    Code Helper (Plugin)   34290    Python         20.2 MB    3h 12m     abhishek
+
+  ⚙ Backend (2)
+  ────────────────────────────────────────────────────────────────────────────
+  5237    Code Helper (Plugin)   34073    Python         20.0 MB    3h 12m     abhishek
+  5932    Code Helper (Plugin)   61773    Python         57.5 MB    58m 39s    abhishek
+```
+
+### Interactive terminal UI
+
+```
+$ ptnix ui
+```
+
+Arrow keys to navigate, enter to inspect, `f` to fix. Full interactive TUI for port management, powered by ratatui.
+
+### Define your dev stack with `.ptnix.toml`
+
+```bash
+$ ptnix init
+
+  ✔ Created .ptnix.toml
+  → Detected Next.js project (port 3050)
+  → Port 3050 found in package.json scripts
+```
+
+ptnix reads your `package.json` scripts and detects hardcoded ports (`--port 3050`, `-p 8080`, etc.). In a monorepo, it scans subdirectories and generates a multi-service config automatically.
+
+Edit the generated config to declare your services:
+
+```toml
+[project]
+name = "my-app"
+
+[services.frontend]
+port = 3000
+run = "npm run dev"
+cwd = "./frontend"
+preflight = true
+
+[services.api]
+port = 8080
+run = "cargo run"
+cwd = "./backend"
+preflight = true
+
+[services.worker]
+port = 9090
+run = "python worker.py"
+env = { PYTHON_ENV = "development" }
+
+[profiles.staging]
+frontend = { port = 3100 }
+api = { port = 8180, env = { RUST_LOG = "info" } }
+```
+
+### Start your entire dev stack
+
+```
+$ ptnix up
+
+  🚀 Starting 3 services...
+
+  ✔ api started on port 8080
+  ✔ frontend started on port 3050
+  ✔ worker started on port 9090
+
+  ✔ 3/3 services started.
+```
+
+Pre-flight checks run automatically. If a port is busy, ptnix tells you. Add `-y` to auto-fix conflicts before starting.
+
+ptnix tracks spawned PIDs in `.ptnix.pids`. If a framework binds a different port than configured (e.g., Next.js auto-increments when a port is taken), ptnix detects the actual port and reports it:
+
+```
+  ✔ frontend started on port 3001 (configured: 3000)
+      ⚠ port 3000 was busy, update .ptnix.toml to match
+```
+
+### Stop everything
+
+```
+$ ptnix down
+
+  🛑 Stopping 3 services...
+
+  ✔ api stopped (port 8080)
+  ✔ frontend stopped (port 3050)
+  ✔ worker stopped (port 9090)
+
+  ✔ 3/3 services stopped.
+```
+
+`down` uses a 3-tier strategy to find and stop processes: checks the declared port, then the actual port from `.ptnix.pids` (if the process moved), then kills by saved PID directly.
+
+### Pre-flight port check
+
+```
+$ ptnix preflight 3000 8080 5432
+
+  🔍 Pre-flight check for 3 ports...
+
+  ✔ Port 3000 is free
+  ✔ Port 8080 is free
+  ✘ Port 5432 is busy -- postgres (PID 1234, PostgreSQL)
+
+  ⚠ 1 port is already in use. Run ptnix fix <port> to fix.
+```
+
+Run without arguments to check all ports from `.ptnix.toml`.
+
+### Watch a port and auto-restart on crash
+
+```
+$ ptnix watch 3000
+
+  👀 Watching port 3000 (every 2s, Ctrl-C to stop)
+
+  ✔ Port 3000 is up -- Next.js (PID 81106)
+  ✘ Port 3000 went down -- Unknown crash reason (was PID 81106)
+  🚀 Auto-restarting: npm run dev
+  ✔ Port 3000 recovered (PID 82001, Next.js) -- downtime: 3s
+```
+
+If a `.ptnix.toml` defines a `run` command for the watched port, ptnix auto-restarts it when it crashes.
+
+### Validate port assignments
+
+```
+$ ptnix registry check
+
+  🔍 Checking port registry...
+
+  ✔ No port conflicts found across 3 services.
+```
+
+Detects duplicate ports across services and profile overrides in `.ptnix.toml`.
+
+### Run all checks in CI
+
+```
+$ ptnix ci
+
+  ▶ Step 1/4: Validate config... ✔
+  ▶ Step 2/4: Registry check... ✔
+  ▶ Step 3/4: Pre-flight check... ✔
+  ▶ Step 4/4: Doctor... ✔
+
+  ✔ All checks passed.
+```
+
+Non-interactive runner for CI/CD pipelines. Runs config validation, registry check, preflight, and doctor in sequence. Exits 1 on failure. Supports `--json`.
+
+### Switch profiles
+
+```
+$ ptnix use staging
+
+  ✔ Switched to profile: staging
+  → frontend port: 3100
+  → api port: 8180
+```
+
+Switch between named profiles defined in `.ptnix.toml`. The active profile is persisted to `.ptnix.state` and applied automatically to `up`, `down`, `watch`, and `preflight`.
+
+### Restart a single service
+
+```
+$ ptnix restart frontend
+
+  🔄 Restarting frontend (port 3000)...
+  ✔ Stopped process on port 3000 (PID 81106)
+  ✔ Started frontend on port 3000
+```
+
+Restarts a named service from `.ptnix.toml`. Stops whatever is on the port (local process or Docker container), then re-runs the configured `run` command. Respects the active profile.
+
+### Check service status
+
+```
+$ ptnix status
+
+  📊 test-app status
+
+  SERVICE      PORT    STATUS     PROCESS           PID
+  ──────────────────────────────────────────────────────
+  frontend     3000    🟢 Running  node              81106
+  api          8080    🔴 Stopped
+  worker       9090    🟡 Conflict python3           92001
+```
+
+Shows the live status of every service in `.ptnix.toml`. Compares the actual process on each port against the expected service to flag conflicts. Supports `--json`.
+
+### Stream logs from a port
+
+```
+$ ptnix log 3000
+```
+
+Streams live logs from the process on a port. Works with Docker containers (`docker logs -f`) and local processes (detects log files via `lsof`). If the process writes to a TTY, suggests how to redirect output to a file.
+
+---
+
+## CLI Commands Reference
+
+| Command                     | Description                                           | Example                                |
+| --------------------------- | ----------------------------------------------------- | -------------------------------------- |
+| `ptnix scan`              | List all listening ports with service, memory, uptime | `ptnix scan`                         |
+| `ptnix <port>`            | Inspect a single port in detail                       | `ptnix 3000`                         |
+| `ptnix fix <ports>`       | Safely kill the process on one or more ports          | `ptnix fix 3000 8080`                |
+| `ptnix fix <ports> --run` | Kill and auto-restart a dev server                    | `ptnix fix 3000 --run "npm run dev"` |
+| `ptnix fix <ports> -y`    | Skip confirmation prompt                              | `ptnix fix 3000 8080 -y`             |
+| `ptnix kill <ports>`      | Direct kill with safety confirmation                  | `ptnix kill 3000 8080`               |
+| `ptnix group`             | Ports organized by role (frontend/backend/db/infra)   | `ptnix group --dev`                  |
+| `ptnix doctor`            | Find stale servers, idle processes, conflicts         | `ptnix doctor`                       |
+| `ptnix doctor -y`         | Auto-fix all safe issues                              | `ptnix doctor -y`                    |
+| `ptnix history`           | View past actions with timestamps                     | `ptnix history`                      |
+| `ptnix history --stats`   | Kill stats: success rate, top ports, top processes    | `ptnix history --stats`              |
+| `ptnix project`           | Detect project type, suggest dev commands             | `ptnix project`                      |
+| `ptnix ui`                | Interactive TUI with keyboard navigation              | `ptnix ui`                           |
+| `ptnix init`              | Create a `.ptnix.toml` (auto-detects ports)         | `ptnix init`                         |
+| `ptnix up`                | Start all services from `.ptnix.toml`               | `ptnix up`                           |
+| `ptnix up -y`             | Start services, auto-fix port conflicts first         | `ptnix up -y`                        |
+| `ptnix down`              | Stop all services from `.ptnix.toml`                | `ptnix down`                         |
+| `ptnix preflight`         | Check if ports are free before starting               | `ptnix preflight 3000 8080`          |
+| `ptnix watch <port>`      | Monitor a port, alert on crash, auto-restart          | `ptnix watch 3000`                   |
+| `ptnix registry check`    | Validate port assignments for conflicts               | `ptnix registry check`               |
+| `ptnix ci`                | Run all checks non-interactively (CI/CD mode)         | `ptnix ci --json`                    |
+| `ptnix use <profile>`     | Switch to a named profile from `.ptnix.toml`        | `ptnix use staging`                  |
+| `ptnix restart <service>` | Restart a named service from `.ptnix.toml`          | `ptnix restart frontend`             |
+| `ptnix status`            | Show live status of all services from config          | `ptnix status`                       |
+| `ptnix log <port>`        | Stream live logs from a port (Docker or local)        | `ptnix log 3000`                     |
+
+> All commands support `--json` for scripting and CI pipelines.
+
+---
+
+## Why ptnix Over kill-port, fkill, or lsof
+
+**It's not `kill -9` with extra steps.**
+
+ptnix is a process classification engine built for developer productivity:
+
+- **Identifies services** -- Next.js, Vite, Django, Flask, Express, PostgreSQL, Redis, Docker, and 13+ categories with confidence scores
+- **Safety system** -- blocks system-critical processes (PID 1, sshd, launchd), warns about databases (data loss risk), approves dev servers
+- **Graceful shutdown** -- SIGTERM first, waits for clean exit, escalates to SIGKILL only if needed
+- **Project-aware** -- reads package.json, Cargo.toml, pyproject.toml to suggest the right restart command
+- **Docker-aware** -- detects container ports vs host ports
+- **History** -- every action logged to `~/.ptnix/history.json` with timestamps and outcomes
+
+### How ptnix works under the hood
+
+1. **Scan** -- queries the OS for all listening ports, resolves PIDs via sysinfo
+2. **Classify** -- identifies the service type (Next.js, PostgreSQL, Docker, etc.)
+3. **Assess** -- safety check: SAFE / WARN / BLOCK
+4. **Strategy** -- picks the right approach: Graceful, Escalating, or Force
+5. **Execute** -- sends signals, waits for exit, verifies the port is free
+6. **Recover** -- detects the project, suggests restart, or auto-restarts with `--run`
+
+### Safety tiers
+
+| Verdict     | Examples                                                    | Behavior                                        |
+| ----------- | ----------------------------------------------------------- | ----------------------------------------------- |
+| **BLOCKED** | PID 0/1, launchd, systemd, sshd, kernel_task                | Refuses to kill                                 |
+| **WARNING** | PostgreSQL, MySQL, Redis, Docker, Nginx                     | Warns about consequences, asks for confirmation |
+| **SAFE**    | Next.js, Vite, Create React App, Django dev, Flask, Node.js | Kills gracefully                                |
+
+---
+
+## Developer Productivity Workflows
+
+### "Port 3000 is already in use" after a crash
+
+Your Next.js server crashed. The port is stuck. You just want to get back to coding.
+
+```bash
+ptnix fix 3000 -y --run "npm run dev"
+```
+
+Port cleared, server restarted. One line.
+
+### Make `npm run dev` crash-proof
+
+Add ptnix to your scripts so port conflicts resolve themselves:
+
+```json
+{
+  "scripts": {
+    "dev": "ptnix fix 3000 -y --run 'next dev'",
+    "dev:api": "ptnix fix 8080 -y --run 'node server.js'",
+    "dev:clean": "ptnix doctor -y && npm run dev"
+  }
+}
+```
+
+Now `npm run dev` works every time, even if something is already on port 3000.
+
+### Morning dev environment reset
+
+You open your laptop. Stale servers from yesterday are hogging ports and memory.
+
+```bash
+ptnix doctor -y
+```
+
+Finds zombie processes, idle servers, and cleans them up automatically.
+
+### "What is using port 8080?"
+
+Something is squatting on your API port but you have no idea what.
+
+```bash
+ptnix 8080
+```
+
+Shows the process name, PID, service type, memory, uptime, project directory, and whether it's safe to kill.
+
+### Full-stack dev with `.ptnix.toml`
+
+Frontend on 3000, API on 8080, worker on 9090. Define them once, manage them forever:
+
+```bash
+# Initialize config
+ptnix init
+
+# Start everything (runs preflight checks automatically)
+ptnix up
+
+# Stop everything at end of day
+ptnix down
+```
+
+No more opening 5 terminals and running commands manually.
+
+### Monitor a flaky dev server
+
+Your dev server keeps crashing. Let ptnix watch it and auto-restart:
+
+```bash
+ptnix watch 3000
+```
+
+If a `.ptnix.toml` defines a `run` command for port 3000, ptnix auto-restarts it when it goes down.
+
+### Pre-flight check before deployment scripts
+
+```bash
+# Check all ports from .ptnix.toml are free
+ptnix preflight
+
+# Check specific ports
+ptnix preflight 3000 8080 5432
+```
+
+### Shell aliases for daily use
+
+```bash
+# ~/.zshrc or ~/.bashrc
+alias pf='ptnix fix'
+alias pfs='ptnix scan'
+alias pfd='ptnix doctor -y'
+alias pu='ptnix up'
+alias pd='ptnix down'
+alias dev3='ptnix fix 3000 -y --run "npm run dev"'
+alias dev8='ptnix fix 8080 -y --run "node server.js"'
+```
+
+### Fix multiple ports at once
+
+Clearing out a full dev environment before starting fresh:
+
+```bash
+# Fix multiple ports in one command
+ptnix fix 3000 8080 5173 -y
+
+# Or with .ptnix.toml
+ptnix down && ptnix up
+```
+
+### CI / pre-commit: ensure clean ports
+
+```bash
+# Run all checks in one command (exits 1 on failure)
+ptnix ci
+
+# Or with JSON output for CI parsing
+ptnix ci --json
+```
+
+### Validate port assignments before deploying
+
+```bash
+# Check for duplicate ports across services and profiles
+ptnix registry check
+```
+
+### Switch between dev and staging
+
+```bash
+# Define profiles in .ptnix.toml, then switch:
+ptnix use staging
+ptnix up
+
+# Switch back to default
+ptnix use default
+ptnix up
+```
+
+### Pipe to scripts with JSON output
+
+```bash
+# Get all listening ports as JSON
+ptnix scan --json | jq '.[] | select(.service == "Next.js")'
+
+# Count active dev servers
+ptnix scan --json | jq '[.[] | select(.service != "Unknown")] | length'
+```
+
+---
+
+## Comparison: ptnix vs kill-port vs fkill
+
+|                        | kill-port | fkill     | **ptnix**                         |
+| ---------------------- | --------- | --------- | ----------------------------------- |
+| Service identification | No        | Name only | Full (service, memory, uptime, CWD) |
+| Safety checks          | No        | No        | Yes (safe / warn / block)           |
+| Graceful shutdown      | No        | No        | Yes (SIGTERM, then escalate)        |
+| Restart hints          | No        | No        | Yes (project-aware)                 |
+| Auto-restart           | No        | No        | Yes (`--run`)                       |
+| Docker awareness       | No        | No        | Yes                                 |
+| Auto-diagnosis         | No        | No        | Yes (`doctor`)                      |
+| Port grouping          | No        | No        | Yes (by role)                       |
+| Action history         | No        | No        | Yes                                 |
+| Interactive TUI        | No        | Yes       | Yes                                 |
+| Project config file    | No        | No        | Yes (`.ptnix.toml`)               |
+| Dev stack up/down      | No        | No        | Yes (`up` / `down`)                 |
+| Service restart        | No        | No        | Yes (`restart <service>`)           |
+| Service status         | No        | No        | Yes (`status`)                      |
+| Log streaming          | No        | No        | Yes (`log <port>`)                  |
+| Port monitoring        | No        | No        | Yes (`watch`)                       |
+| Pre-flight checks      | No        | No        | Yes (`preflight`)                   |
+| Crash detection        | No        | No        | Yes (signal, OOM, zombie)           |
+| Port registry          | No        | No        | Yes (conflict detection)            |
+| CI/CD mode             | No        | No        | Yes (`ci` command)                  |
+| Profiles               | No        | No        | Yes (`use` for dev/staging/prod)    |
+| Platform               | Node.js   | Node.js   | Native binary                       |
+| Size                   | ~50MB     | ~50MB     | ~1.2MB                              |
+
+---
+
+## Architecture & Performance
+
+```
+src/
+  scanner/      Batch port scanning with sysinfo process resolution
+  classifier/   13+ service classifiers with confidence scoring
+  engine/       Safety checks, strategy selection, graceful kill with retry
+  platform/     macOS (lsof + libc) / Linux (/proc/net/tcp) / Windows (netstat)
+  project/      Filesystem project detection (package.json, Cargo.toml, etc.)
+  docker/       Container awareness via docker ps
+  grouping/     Port role classification (frontend/backend/database/infra)
+  doctor/       Stale servers, idle processes, crowded ports
+  history/      Action log persisted to ~/.ptnix/history.json
+  config/       .ptnix.toml project config loader (monorepo, port detection)
+  watch/        Continuous port monitoring with crash detection
+  stack/        Dev stack orchestration (up/down with PID tracking)
+  preflight/    Pre-flight port availability checks
+  crash/        Crash reason detection (signal, OOM, zombie)
+  restart/      Single-service restart (stop + start from config)
+  status/       Live service status dashboard (running/stopped/conflict)
+  log/          Log streaming for Docker containers and local processes
+  registry/     Port conflict detection across services and profiles
+  ci/           Non-interactive CI/CD runner (config + registry + preflight + doctor)
+  plugin/       Extensible ServiceDetector trait for custom detectors
+  cli/          Clap v4 + colored output + ratatui TUI
+```
+
+Built in Rust for speed and reliability. Ships as a single ~1.2MB static binary with zero runtime dependencies. No Node.js, no Python -- just a fast native CLI tool for managing ports and debugging dev environments.
+
+---
+
+## Contributing
+
+```bash
+git clone https://github.com/abhishekayu/ptnix.git
+cd ptnix
+cargo build
+cargo test
+```
+
+- Report bugs or request features via [Issues](https://github.com/abhishekayu/ptnix/issues)
+- Add new service classifiers
+- Improve platform support
+- Write new doctor diagnostics
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for details.
+
+---
+
+## VS Code Extension
+
+Manage ports and services directly from the VS Code sidebar -- no terminal needed.
+
+[![Install from VS Code Marketplace](https://img.shields.io/badge/VS%20Code-Install%20Extension-007ACC?logo=visual-studio-code)](https://marketplace.visualstudio.com/items?itemName=abhishekayu.ptnix)
+
+**Features:**
+
+- Sidebar dashboard showing all listening ports with process info
+- Project-aware service management (reads `.ptnix.toml`)
+- One-click Start All, Stop All, Fix, Doctor, Preflight, and 15+ actions
+- Switch between dev/staging/production profiles
+- Auto-install and update the ptnix CLI binary
+
+```bash
+code --install-extension abhishekayu.ptnix
+```
+
+[View on Marketplace](https://marketplace.visualstudio.com/items?itemName=abhishekayu.ptnix)
+
+---
+
+## License
+
+[MIT](LICENSE) -- free for personal and commercial use.
+
+---
+
+<p align="center">
+  <strong>ptnix</strong> -- an open-source CLI tool for port management, process debugging, and developer environment recovery.<br>
+  Built for developers who are tired of <code>lsof</code> + <code>kill -9</code>.<br>
+  Define your dev stack in <code>.ptnix.toml</code>, start with <code>ptnix up</code>, stop with <code>ptnix down</code>.<br>
+  Restart a service with <code>ptnix restart frontend</code>, check status with <code>ptnix status</code>.<br>
+  Switch profiles with <code>ptnix use staging</code>, validate with <code>ptnix ci</code>.<br>
+  Works with Next.js, Vite, Django, Flask, Express, Docker, PostgreSQL, Redis, and more.
+</p>

package/bin/ptnix.js

@@ -0,0 +1,45 @@
+#!/usr/bin/env node
+
+"use strict";
+
+const { execFileSync } = require("child_process");
+const path = require("path");
+const fs = require("fs");
+
+const binDir = path.join(__dirname);
+
+function getBinaryPath() {
+  const platform = process.platform;
+  const arch = process.arch;
+
+  let binaryName = "ptnix";
+  if (platform === "win32") {
+    binaryName = "ptnix.exe";
+  }
+
+  const binaryPath = path.join(binDir, binaryName);
+  if (fs.existsSync(binaryPath)) {
+    return binaryPath;
+  }
+
+  console.error(
+    `ptnix binary not found for ${platform}-${arch}.`,
+    `\nRun 'npm rebuild ptnix-cli' or install via: curl -fsSL https://raw.githubusercontent.com/abhishekayu/ptnix/main/install.sh | sh`,
+  );
+  process.exit(1);
+}
+
+const binary = getBinaryPath();
+const args = process.argv.slice(2);
+
+try {
+  const result = execFileSync(binary, args, {
+    stdio: "inherit",
+    env: process.env,
+  });
+} catch (err) {
+  if (err.status !== undefined) {
+    process.exit(err.status);
+  }
+  process.exit(1);
+}

package/install.js

@@ -0,0 +1,95 @@
+"use strict";
+
+const https = require("https");
+const fs = require("fs");
+const path = require("path");
+const { execSync } = require("child_process");
+const os = require("os");
+
+const VERSION = require("./package.json").version;
+const REPO = "abhishekayu/ptnix";
+
+function getPlatformInfo() {
+  const platform = process.platform;
+  const arch = process.arch;
+
+  const platformMap = {
+    "darwin-x64": "ptnix-darwin-x86_64",
+    "darwin-arm64": "ptnix-darwin-aarch64",
+    "linux-x64": "ptnix-linux-x86_64",
+    "linux-arm64": "ptnix-linux-aarch64",
+    "win32-x64": "ptnix-windows-x86_64",
+  };
+
+  const key = `${platform}-${arch}`;
+  const name = platformMap[key];
+
+  if (!name) {
+    console.error(`Unsupported platform: ${key}`);
+    console.error("Install manually: cargo install ptnix-cli");
+    process.exit(0); // Don't fail npm install
+  }
+
+  const ext = platform === "win32" ? ".zip" : ".tar.gz";
+  return { name, ext, platform };
+}
+
+function download(url) {
+  return new Promise((resolve, reject) => {
+    https
+      .get(url, (res) => {
+        if (
+          res.statusCode >= 300 &&
+          res.statusCode < 400 &&
+          res.headers.location
+        ) {
+          return download(res.headers.location).then(resolve).catch(reject);
+        }
+        if (res.statusCode !== 200) {
+          return reject(new Error(`HTTP ${res.statusCode} for ${url}`));
+        }
+        const chunks = [];
+        res.on("data", (chunk) => chunks.push(chunk));
+        res.on("end", () => resolve(Buffer.concat(chunks)));
+        res.on("error", reject);
+      })
+      .on("error", reject);
+  });
+}
+
+async function install() {
+  const { name, ext, platform } = getPlatformInfo();
+  const url = `https://github.com/${REPO}/releases/download/v${VERSION}/${name}${ext}`;
+  const binDir = path.join(__dirname, "bin");
+
+  console.log(
+    `Downloading ptnix v${VERSION} for ${process.platform}-${process.arch}...`,
+  );
+
+  try {
+    const data = await download(url);
+    const tmpFile = path.join(os.tmpdir(), `${name}${ext}`);
+    fs.writeFileSync(tmpFile, data);
+
+    if (platform === "win32") {
+      // Use PowerShell to extract zip
+      execSync(
+        `powershell -Command "Expand-Archive -Force '${tmpFile}' '${binDir}'"`,
+        { stdio: "pipe" },
+      );
+    } else {
+      execSync(`tar xzf "${tmpFile}" -C "${binDir}"`, { stdio: "pipe" });
+      const binary = path.join(binDir, "ptnix");
+      fs.chmodSync(binary, 0o755);
+    }
+
+    fs.unlinkSync(tmpFile);
+    console.log("ptnix installed successfully.");
+  } catch (err) {
+    console.error(`Failed to download ptnix: ${err.message}`);
+    console.error("Install manually: cargo install ptnix-cli");
+    // Don't fail npm install
+  }
+}
+
+install();

package/package.json

@@ -0,0 +1,49 @@
+{
+  "name": "ptnix-cli",
+  "version": "0.5.6",
+  "description": "ptnix — blazing fast port & process manager. Kill and list processes on ports from your terminal.",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/abhishekayu/ptnix"
+  },
+  "license": "MIT",
+  "keywords": [
+    "port",
+    "kill-port",
+    "port-conflict",
+    "developer-tools",
+    "cli",
+    "devserver",
+    "process",
+    "debug",
+    "eaddrinuse",
+    "zombie-process",
+    "port-scanner",
+    "dev-environment",
+    "productivity"
+  ],
+  "bin": {
+    "ptnix": "bin/ptnix.js"
+  },
+  "files": [
+    "bin/",
+    "install.js",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "postinstall": "node install.js"
+  },
+  "os": [
+    "darwin",
+    "linux",
+    "win32"
+  ],
+  "cpu": [
+    "x64",
+    "arm64"
+  ],
+  "engines": {
+    "node": ">=16"
+  }
+}