Recordsnpmexeca
Change the conditions
Current conditions
execa @5.1.1ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 4 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
- 13 / 13
- Contract verifications
- 0 / 4
- Usage records
- 3
- Independent reporting peers
- 2
- Last recorded
- 2026-09-03
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 4 passed
Verified — this network ran a contract at this coordinate.
-
execa.sync
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
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.
| Library | 9.6.1 | 8.0.1 | 5.1.1 |
|---|---|---|---|
| get-stream | 9.0.1 | 8.0.1 | 6.0.1 |
| human-signals | 8.0.1 | 5.0.0 | 2.1.0 |
| is-stream | 4.0.1 | 3.0.0 | 2.0.1 |
| npm-run-path | 6.0.0 | 5.3.0 | 4.0.1 |
| onetime | — | 6.0.0 | 5.1.2 |
| signal-exit | 4.1.0 | 4.1.0 | 3.0.7 |
| strip-final-newline | 4.0.0 | 3.0.0 | 2.0.0 |
| @sindresorhus/merge-streams | 4.0.0 | — | — |
| cross-spawn | 7.0.6 | 7.0.6 | 7.0.6 |
| figures | 6.1.0 | — | — |
| is-plain-obj | 4.1.0 | — | — |
| merge-stream | — | 2.0.0 | 2.0.0 |
| pretty-ms | 9.3.1 | — | — |
| yoctocolors | 2.2.0 | — | — |
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.