CodeSampleX

Recordsnpm@types/node26.2.0

Change the conditions
Fixed
OSalpine musl Package version26.2.0
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

@types/node @26.2.0alpine musl · x64 · node 22 · npm · node

package-level total, not an API

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
2 / 2
Contract verifications
1 / 1
Usage records
4
Independent reporting peers
1
Last recorded
2026-09-08
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

26.2.0

executionContext=node

66 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
undici-types 8.3.0 CANDIDATE Correlated change; unproven combination contract passed 28 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.

Library26.5.126.4.126.4.026.2.026.1.224.13.524.13.322.20.322.20.222.20.122.19.122.10.220.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.

Recent failure clusters