CodeSampleX

Recordsnpmeslint-scope9.1.2

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

Current conditions

eslint-scope @9.1.2windows 11 · x64 · node 24 · npm 11 · 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
1
Independent reporting peers
1
Last recorded
2026-08-13

Dependencies

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

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.