CodeSampleX

Recordsnpmeslint-scope8.4.0

Change the conditions
Fixed
Package version8.4.0 Symbolwhole package Package managernpm 11
Filter OSwindows 11 Runtimenode 24 Architecturex64 Execution contextnode Clear filters

Current conditions

eslint-scope @8.4.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

10 of 12 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 (3)

Project observations
10 / 12
Contract verifications
nothing at this coordinate
Usage records
12
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-21
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
esrecurse 4.3.0 contract passed 5 project-days
estraverse 5.3.0 contract passed 5 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.0
@types/esrecurse 4.3.1 —
@types/estree 1.0.9 —
esrecurse 4.3.0 4.3.0
estraverse 5.3.0 5.3.0

Moved: 0 · unchanged at every release: 4

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