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
- 11 / 11
- Contract verifications
- 0 / 4
- Usage records
- 3
- Independent reporting peers
- 2
- Last recorded
- 2026-08-31
Evidence you can open
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.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| cross-spawn | 7.0.6 | contract passed | 6 project-days |
| get-stream | 6.0.1 | contract passed | 6 project-days |
| human-signals | 2.1.0 | contract passed | 5 project-days |
| is-stream | 2.0.1 | contract passed | 5 project-days |
| merge-stream | 2.0.0 | contract passed | 5 project-days |
| npm-run-path | 4.0.1 | contract passed | 5 project-days |
| onetime | 5.1.2 | contract passed | 5 project-days |
| signal-exit | 3.0.7 | contract passed | 4 project-days |
| strip-final-newline | 2.0.0 | contract passed | 4 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.