mafintosh/why-is-node-running
Node is running but you don't know why? why-is-node-running is here to help you. observed · 2026-10-21
Health v2 · maintenance only
88/100
- Activity 99
- Release rhythm 67
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.
- gap_med: 354.0
- age_days: 3906
- days_rel: 11
- days_push: 11
- n_releases_24m: 3
Adoption not part of the score
1948 stars · 52 forks observed · 2026-10-21
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
why-is-node-running is a Node.js library and CLI that logs the active handles (timers, servers, etc.) keeping a Node process running. It can be used programmatically, via a CLI wrapper, or preloaded with Node's --import flag.
Use cases
- find out why my node process won't exit
- debug lingering timers and open servers in node
- log active handles keeping node running
- diagnose hanging node scripts
- inspect what keeps the event loop alive
When to choose
- a Node.js process stays alive and you don't know which handles are responsible
- you want a quick CLI or signal-based way to dump active handles with stack traces
When to avoid
- debugging non-Node.js processes
- you need full CPU/memory profiling rather than handle inspection
Facets
library · maturity active
developer-tools monitoring logging developer-tools backend cli cross-platform debugging nodejs event-loop handles diagnostics
2 sources
- readme: https://github.com/mafintosh/why-is-node-running · fetched 2026-10-21 · 9e36a93f2b40
- registry_npm: https://registry.npmjs.org/why-is-node-running · fetched 2026-08-29 · 8d6ec8486c0d
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| mafintosh/why-is-node-running | main | 88 |
For agents
markdown · JSON · MCP: product_card(name="mafintosh/why-is-node-running")
Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem