why-is-node-running
The focused repository has a clear README, bundled types, a matching source project, and release notes for this version. Workflow pinning and security documentation are weak, while recent development activity is absent; pin this version rather than relying on rapid fixes.
68%
Total Score
50
90
67
Health Score Breakdown
The repository is owned by an individual rather than an organization, so continuity depends on a relatively narrow project owner base. Other signals show a mature, maintained history but not current activity.
The package has 24 releases since 2016, but none in the last 12 months and its latest release was about 20 months ago. This indicates slowing maintenance for a mature utility.
There were no commits and no active maintainers in the last three months. Combined with the long release gap, this raises abandonment and response-time concerns.
No build tools or security scanning tools were detected. For this small package that is a modest transparency and maintenance gap, not evidence of unfitness by itself.
The repository has no security policy. This weakens vulnerability-reporting transparency, although the package remains small and clearly documented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 10 years ago
- Unpacked Size
- 0.1 MB
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.