npm · npm:why-is-node-running
why-is-node-running active
Node is running but you don't know why? why-is-node-running is here to help you.
The latest stable version of why-is-node-running is 3.2.3, published on 2026-10-09. Verified by Vigia on 2026-11-12.
| Latest stable version | 3.2.3 |
|---|---|
| Published | 2026-10-09 11:19:32 UTC |
| Install | npm install why-is-node-running@latest |
| Requires (engines) | {"node":">=20.11"} |
| Peer dependencies | — |
| Dist-tags | latest: 3.2.3 |
| License | MIT |
| Advisories on latest version | none known |
| Last verified | 2026-11-12 13:39:03 UTC |
| Sources | api.deps.dev, registry.npmjs.org, registry.npmjs.org |
Is your project affected?
Check my whole package.jsonGet notified of new versions (Atom)Facts for my AGENTS.md
Free, no signup. Paste your manifest and see what is outdated, deprecated or vulnerable.
Maintenance
| Activity | active |
|---|---|
| Last stable release | 2026-10-09 11:19:32 UTC · 34 days ago |
| Stable releases in the last 12 months | 1 |
| Published versions | 25 |
Heuristic based only on release dates; it does not measure issue or security response times.
Version history
| Version | Published |
|---|---|
3.2.3 | 2026-10-09 11:19:32 UTC |
3.2.2 | 2025-01-08 15:02:27 UTC |
3.2.1 | 2024-10-29 17:08:48 UTC |
3.2.0 | 2024-07-12 17:22:33 UTC |
3.1.0 | 2024-07-09 17:08:19 UTC |
3.0.0 | 2024-07-08 12:59:09 UTC |
2.3.0 | 2024-07-08 12:57:23 UTC |
2.2.2 | 2022-04-26 14:19:06 UTC |
2.2.1 | 2022-01-27 15:30:36 UTC |
2.2.0 | 2020-06-16 20:47:14 UTC |
2.1.2 | 2020-03-07 13:26:25 UTC |
2.1.1 | 2020-03-06 20:48:10 UTC |
2.1.0 | 2019-04-03 14:45:31 UTC |
2.0.3 | 2018-08-30 20:50:06 UTC |
2.0.2 | 2018-03-05 12:05:54 UTC |
2.0.1 | 2018-03-01 12:46:14 UTC |
2.0.0 | 2018-02-14 16:35:32 UTC |
1.2.3 | 2017-10-18 12:32:28 UTC |
1.2.2 | 2016-03-24 21:31:28 UTC |
1.2.1 | 2016-02-16 10:25:17 UTC |
Showing the 20 most recent of 25 versions. JSON
Version compatibility
Newest stable version that declares support for each runtime version (from the requirements published with each version).
| Runtime | Newest compatible version |
|---|---|
node 16 | 2.3.0 |
node 18 | 2.3.0 |
node 20 | 3.2.3 |
node 22 | 3.2.3 |
node 24 | 3.2.3 |
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What is the latest version of why-is-node-running?
The latest stable version of why-is-node-running is 3.2.3, published on 2026-10-09. Verified by Vigia on 2026-11-12.
How do I install the latest version of why-is-node-running?
Run npm install why-is-node-running@latest. The latest stable version is 3.2.3 (verified 2026-11-12).
Is why-is-node-running deprecated?
No. why-is-node-running is not marked as deprecated in the registry.
Which Node.js version does why-is-node-running require?
why-is-node-running 3.2.3 declares this requirement: {"node":">=20.11"}.
Does why-is-node-running 3.2.3 have known vulnerabilities?
No known advisories affect why-is-node-running 3.2.3 according to the data Vigia checks.
Is why-is-node-running still maintained?
why-is-node-running published 1 stable releases in the last 12 months; the most recent was 34 days ago. Activity: active.
Observed changes
- Fri Oct 09 2026 11:35:45 GM +0000 (Coordinated Universal Time) — released 3.2.2 → 3.2.3
Related packages
- aggregate-error
- google-auth-library
- @aws-sdk/xml-builder
- setimmediate
- read-pkg
- @types/ms
- read-cache
- @smithy/smithy-client
- @aws-sdk/middleware-recursion-detection
- react-hook-form
- methods
- @tailwindcss/oxide-linux-x64-musl
Badges for your README
Show the latest version, maintenance status and deprecation status of this package. Copy the Markdown:
[](https://vigia.coredls.cloud/npm/why-is-node-running) [](https://vigia.coredls.cloud/npm/why-is-node-running) [](https://vigia.coredls.cloud/npm/why-is-node-running)
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/why-is-node-running
GET https://vigia.coredls.cloud/v1/packages/npm/why-is-node-running/versions/{version}