CodeSampleX

Recordsnpmrollup4.62.5

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

Current conditions

rollup @4.62.5ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

13 of 18 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
13 / 18
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
2
Failures with a captured fingerprint
0 / 5
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

4.62.5

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

5 FAIL · stage: PROJECT_PROCESS

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

Library4.63.34.63.24.63.14.63.04.62.54.62.44.62.34.54.04.34.84.24.0
@types/estree 1.0.9 1.0.9 1.0.9 1.0.9 1.0.9 1.0.9 1.0.9 1.0.8 1.0.6 1.0.6

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