Is node-ipc healthy, maintained, and safe?
No — node-ipc carries 1 unpatched critical advisory and should not be adopted without a remediation plan.
The verdict
On the OSPulse health scale, node-ipc lands at 40/100 — medium risk, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — node-ipc carries 1 unpatched critical advisory and should not be adopted without a remediation plan.
Its most recent release shipped on 14 May 2026 — 74 days ago — so development is clearly active. Across 82 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
OSV lists 4 known advisories for node-ipc, including 1 critical. Open critical advisories are the strongest possible signal to pin to a patched version, replace, or fork before shipping. Each advisory is listed with its OSV/GHSA identifier below.
node-ipc is usable but carries real signals — pin versions, watch for new advisories, and keep a fallback in mind. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (4)
node-ipc behavior change
Hidden functionality in node-ipc
Embedded Malicious Code in node-ipc
Malicious code in node-ipc (npm)
Key facts
- Latest version
- v12.0.0
- Last release
- 14 May 2026 (74 days ago)
- Total releases
- 82
- First release
- 22 February 2014
- Package age
- 12.4 years
- Maintainers
- 1
- Known advisories
- 4
- Confidence
- High
Frequently asked
Is node-ipc still maintained?
Yes — node-ipc released as recently as 14 May 2026 (74 days ago), so it is actively maintained.
Does node-ipc have known security vulnerabilities?
Yes — OSV lists 4 advisories for node-ipc, including 1 rated critical. See the advisory list on this page for the OSV/GHSA identifiers.
Is node-ipc safe to use?
No — node-ipc carries 1 unpatched critical advisory and should not be adopted without a remediation plan. OSPulse rates it 40/100 (medium risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
node-ipc is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.