Recordsnpm@npmcli/run-script
Change the conditions
Current conditions
@npmcli/run-script @9.1.0debian glibc · x64 · node 22 · npm · node
2 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (2)
- Project observations
- 2 / 2
- Contract verifications
- 2 / 2
- Usage records
- 6
- Independent reporting peers
- 1
- Last recorded
- 2026-10-18
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
runScript
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
9.1.0
linux · node@22.23 · moduleSystem=esm · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:536db39a2e089f7ed603954e4a67695a077090ed80e3d0d1ef21bd2d6a9e9b21
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @npmcli/node-gyp | 4.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 21 project-days |
| @npmcli/package-json | 6.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 21 project-days |
| @npmcli/promise-spawn | 8.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 20 project-days |
| node-gyp | 11.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 20 project-days |
| proc-log | 5.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 20 project-days |
| which | 5.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 20 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 | 10.0.4 | 10.0.3 | 9.1.0 |
|---|---|---|---|
| @npmcli/node-gyp | 5.0.0 | 5.0.0 | 4.0.0 |
| @npmcli/package-json | 7.0.5 | 7.0.4 | 6.2.0 |
| @npmcli/promise-spawn | 9.0.1 | 9.0.1 | 8.0.3 |
| node-gyp | 12.4.0 | 12.1.0 | 11.5.0 |
| proc-log | 6.1.0 | 6.1.0 | 5.0.0 |
| which | — | 6.0.0 | 5.0.0 |
Moved: 6 · unchanged at every release: 0
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.