CodeSampleX

Recordsnpm@npmcli/promise-spawn8.0.3promiseSpawn

Change the conditions
Fixed
SymbolpromiseSpawn
Filter OSdebian glibc Runtimenode 22 Package version8.0.3 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

promiseSpawn @8.0.3debian glibc · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-18
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

8.0.3

linux · node@22.23 · moduleSystem=esm · executionContext=node

2 FAIL · stage: UNKNOWN · fingerprint: sha256:536db39a2e089f7ed603954e4a67695a077090ed80e3d0d1ef21bd2d6a9e9b21

View exact conditions View failure cluster
Library Version Health Measured there Projects
which 5.0.0 CANDIDATE Correlated change; unproven combination contract passed 32 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.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Library9.0.18.0.3
which 6.0.0 5.0.0

Moved: 1 · unchanged at every release: 0

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters