CodeSampleX

Recordsnpmexeca9.6.1

Change the conditions
Fixed
Package version9.6.1 Architecturex64 Package manageryarn 4
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Execution contextnode libcglibc Clear filters

Current conditions

execa @9.6.1ubuntu glibc · x64 · node 22 · yarn 4 · node

package-level total, not an API

4 of 4 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
4 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 6

First observed break

9.6.1

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
get-stream 9.0.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
human-signals 8.0.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
is-stream 4.0.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
npm-run-path 6.0.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
signal-exit 4.1.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
strip-final-newline 4.0.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@sindresorhus/merge-streams 4.0.0 PASS All observations passed contract passed 2 project-days
cross-spawn 7.0.6 PASS All observations passed contract passed 2 project-days
figures 6.1.0 PASS All observations passed contract passed 1 project-day
is-plain-obj 4.1.0 PASS All observations passed contract passed 1 project-day
pretty-ms 9.3.1 PASS All observations passed contract passed 1 project-day
yoctocolors 2.2.0 PASS All observations passed contract passed 1 project-day

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.

Moved: 7 · unchanged at every release: 7

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