CodeSampleX

Recordsnpmwhy-is-node-running2.3.0

Change the conditions
Fixed
Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Package version2.3.0 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

why-is-node-running @2.3.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 22 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
81 / 87
Contract verifications
0 / 22
Usage records
37
Independent reporting peers
3
Failures with a captured fingerprint
2 / 6
Last recorded
2026-09-10

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

2.3.0

windows · node@24.13 · executionContext=node · moduleSystem=esm

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

Library Version Health Measured there Projects
siginfo 2.0.0 PASS All observations passed contract passed 42 project-days
stackback 0.0.2 PASS All observations passed contract passed 42 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Recent failure clusters