Recordsnpmbuilder-util-runtime
Change the conditions
Current conditions
builder-util-runtime @9.2.10ubuntu 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
- 23 / 24
- Contract verifications
- 0 / 4
- Usage records
- 1
- Independent reporting peers
- 2
- Last recorded
- 2026-09-14
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.
-
builder-util-runtime.CancellationToken
3 of 3 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
9.2.10
windows · executionContext=node
6 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| debug | 4.4.3 | PASS All observations passed | contract passed | 25 project-days |
| sax | 1.6.1 | PASS All observations passed | contract passed | 25 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: 0 · unchanged at every release: 2
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.