CodeSampleX

Recordsnpm@rollup/pluginutils5.4.0

Change the conditions
Fixed
OSdebian glibc
Filter Runtimenode 22 Package version5.4.0 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

@rollup/pluginutils @5.4.0debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
3
Independent reporting peers
1
Last recorded
2026-09-03

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 3 · Steady 0

First observed break

5.4.0 @types/estree@1.0.9

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2

Library Version Health Measured there Projects
@types/estree 1.0.9 FAIL Linked failure observed; version changed across releases contract passed 29 project-days
estree-walker 2.0.2 FAIL Linked failure observed on this release contract passed 29 project-days
picomatch 4.0.7 FAIL Linked failure observed; version changed across releases contract passed 29 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.

Library5.4.05.3.0
@types/estree 1.0.9 1.0.8
picomatch 4.0.7 4.0.3
estree-walker 2.0.2 2.0.2

Moved: 2 · unchanged at every release: 1

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 16 recorded failure clusters. The rest are single reports.