CodeSampleX

Recordsnpmwhy-is-node-running2.3.0

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

Current conditions

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

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
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 · moduleSystem=esm · executionContext=node

31 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