CodeSampleX

Recordsnpm@types/node26.4.1

Change the conditions
Fixed
Package version26.4.1 Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@types/node @26.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 12 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
101 / 102
Contract verifications
0 / 12
Usage records
10
Independent reporting peers
3
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

26.4.1

linux · node@22.23 · moduleSystem=cjs · executionContext=node

11 FAIL · stage: UNKNOWN · fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef

Library Version Health Measured there Projects
undici-types 8.3.0 CANDIDATE Correlated change; unproven combination contract passed 110 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.120.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.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

Showing the 12 most-reported of 13 recorded failure clusters. The rest are single reports.