CodeSampleX

Recordsnpmrollup4.63.1rollup.rollup

Change the conditions
Fixed
Package version4.63.1 Symbolrollup.rollup
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

rollup.rollup @4.63.1ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 7 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
10 / 10
Contract verifications
0 / 7
Independent reporting peers
2
Last recorded
2026-09-03

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

4.63.1

executionContext=node

40 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

Library Version Health Measured there Projects
@types/estree 1.0.9 CANDIDATE Correlated change; unproven combination contract passed 71 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

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