Recordsnpmexeca9.6.1
Change the conditions
Current conditions
execa @9.6.1ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 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 failed
- Project observations
- 2 / 2
- Contract verifications
- 0 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
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.
| 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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 8.0.1 → 9.6.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate