Recordsnpm@types/node
Change the conditions
Current conditions
@types/node.version @22.20.1x64 · node 22 · node
1 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 came back clean (1)
- Project observations
- 3 / 3
- Contract verifications
- 1 / 1
- Independent reporting peers
- 2
- Last recorded
- 2026-08-26
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
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
22.20.1
executionContext=node
66 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| undici-types | 6.21.0 | CANDIDATE Correlated change; unproven combination | contract passed | 11 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 | 26.5.1 | 26.4.1 | 26.4.0 | 26.2.0 | 26.1.2 | 24.13.5 | 24.13.3 | 22.20.3 | 22.20.2 | 22.20.1 | 22.19.1 | 22.10.2 | 20.19.43 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| undici-types | 8.9.0 | 8.3.0 | 8.3.0 | 8.3.0 | 8.3.0 | 7.18.2 | 7.18.2 | 6.21.0 | 6.21.0 | 6.21.0 | 6.21.0 | 6.20.0 | 6.21.0 |
Moved: 1 · 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.