CodeSampleX

Recordsnpmexeca5.1.1execa.sync

Change the conditions
Fixed
Package version5.1.1 Symbolexeca.sync Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

execa.sync @5.1.1ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 2

First observed break

5.1.1

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:054c93088b95acdec26c27553355ea7447db339349572fdd4ba431478ecb744a

Library Version Health Measured there Projects
get-stream 6.0.1 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
human-signals 2.1.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
is-stream 2.0.1 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
npm-run-path 4.0.1 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
onetime 5.1.2 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
signal-exit 3.0.7 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
strip-final-newline 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
cross-spawn 7.0.6 PASS All observations passed contract passed 8 project-days
merge-stream 2.0.0 PASS All observations passed contract passed 7 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.

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