I am definitely going to give this the beans on every platform I can, because if it delivers… incredibly useful.
Holy shit. An Indian solo dev built the one terminal tool every developer has been missing for 20 years.
It's called witr. It answers one question your OS refuses to answer:
Why is this running?
You see a weird process eating your RAM. You see a port that should not be open. You see a service you do not remember installing. Every tool tells you it exists. None of them tell you why it exists.
ps shows you the process. lsof shows you the port. systemctl shows you the service. But none of them show you the chain. The shell that spawned the supervisor that started the daemon that opened the socket.
witr does.
You type one command. It traces the whole causality. From kernel to PID to parent process to the launchd job or systemd unit that started it. From the open port back to the binary that bound it. From the service back to the user shell that triggered it.
The thing your OS hides, witr surfaces in plain English.
Here is what makes it different from every "process viewer" before this:
→ Traces full causality chains, not just PIDs and ports
→ Interactive TUI dashboard, not a wall of text
→ Single static Go binary, installs in 5 seconds
→ Works on Linux, macOS, Windows, and FreeBSD natively
→ Already packaged on brew, conda, AUR, winget, npm, scoop, chocolatey, FreeBSD ports, and 6 more
→ Detects supervisor chains, container parents, and systemd unit ancestry
→ Flags processes listening on public interfaces or running from suspicious working directories
→ Spots memory hogs and processes that have been running silently for months
Killed: every "what is this process" Stack Overflow rabbit hole, every Reddit thread asking "why is my Mac running this", and every PowerShell one-liner you copied from a 2014 forum post.
15,104 stars in 5 months. 401 forks. 34 contributors. 18 releases. Apache-2.0.
Pranshu Parmar shipped this from his laptop. No VC. No team. No accelerator.
Your OS finally tells you the truth.
(Link in the comments)