why-is-node-running
/All repositories
Overview
HEALTH SCORE
Concerning
40out of 100
Maintainer coverage is the lead risk. Development cadence and security posture are present but not enough to offset the structural risk.
LIFECYCLE
Active
Consistent commits, responsive maintainers, regular releases, and healthy issue triage.
Health breakdown
Concerning(40/100)
Maintainer availability, known risks and supply chain posture, and whether the project is actively developed or appropriately stable.
Maintainer responsiveness
Median response time is 89 days, but most repositories have response times over 90 days.
Bus factor
Only 1 active maintainer currently has merge rights.
Organization Diversity
Contributors span 14 organizations.
Project Achievements
Leaderboards
About
A Node.js debugging utility that helps identify why Node processes stay running by showing active handles that are keeping the event loop alive
First commit
Software value
$7.3K
License(s)
MIT
Data sources
Git
GitHub