pranshuparmar/witr
Why is this running? Trace any process, port, container, or file back to what started it - CLI + TUI.
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
1 release in the last 90 days, the latest 35 days ago, with 45 contributors on GitHub.
Peaked at #6 in the weekly ranking the week of Aug 2, its best in the past year.
Use Cases & Benefits
- Traces any running process, port, container, or file back to its origin with a CLI and interactive TUI for clear causality visualization.
- Provides explicit, human-readable causal chains explaining why a process exists, reducing manual correlation across multiple system tools.
- Use for troubleshooting complex process hierarchies and dependencies in multi-layered environments like containers and service supervisors.
- Use for incident response to quickly identify the root cause of unexpected or unknown running services across Linux, macOS, Windows, and FreeBSD.
- Use for system administrators needing real-time interactive dashboards to monitor and manage processes, ports, and their ancestry on diverse platforms.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
📖 Read the story behind witr
witr exists to answer a single question:
Why is this running?
When something is running on a system, whether it is a process, a service, or something bound to a port, there is always a cause. That cause is often indirect, non-obvious, or spread across multiple layers such as supervisors, containers, services, or shells.
Existing tools (
ps,top,lsof,ss,systemctl,docker ps) expose state and metadata. They show what is running, but leave the user to infer why by manually correlating outputs across tools.witr makes that causality explicit.
It explains where a running thing came from, how it was started, and what chain of systems is responsible for it existing right now, in a single, human-readable output or an interactive TUI dashboard.
witr is distributed as a single static binary for Linux, macOS, FreeBSD, and Windows.
witr is also independently packaged and maintained across multiple operating systems and ecosystems. An up-to-date overview of packaging status is available on Repology. Please note that community packages may lag GitHub releases due to independent review and validation.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
+1,692 stars over 90 days across 21 snapshot days; best day +55 on Aug 12.
Forks
810+67
Open issues
6-6
Compared with peers in Backend
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 8, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| anthropics/skills | 192.3K | +5.2K | 75 | — |
| zed-industries/zed | 94.7K | +2.3K | 75 | 6 days ago |
| google/skills | 23.8K | +2.0K | 75 | — |
| NationalSecurityAgency/ghidra | 99.4K | +1.8K | 75 | 19 days ago |
| DuarteSantos8/openGym | 20.8K | +1.7K | 75 | 7 days ago |
| pranshuparmar/witr | 23.0K | — | 61 | 35 days ago |
| Category median | 94.7K | +2.0K | 75 | — |
Discover Repositories
Search across tracked repositories by name or description