CodeSampleX

Recordsnpmeslint-scope9.1.2

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

Current conditions

eslint-scope @9.1.2debian 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
7
Independent reporting peers
2
Last recorded
2026-09-06

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 3

First observed break

9.1.2

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
estraverse 5.3.0 CANDIDATE Correlated change; unproven combination contract passed 58 project-days
@types/esrecurse 4.3.1 PASS All observations passed contract passed 57 project-days
@types/estree 1.0.9 PASS All observations passed contract passed 58 project-days
esrecurse 4.3.0 PASS All observations passed contract passed 57 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.

Library9.1.28.4.07.2.25.1.1
estraverse 5.3.0 5.3.0 5.3.0 4.3.0
@types/esrecurse 4.3.1 — — —
@types/estree 1.0.9 — — —
esrecurse 4.3.0 4.3.0 4.3.0 4.3.0

Moved: 1 · unchanged at every release: 3

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