CodeSampleX

Compatibilitynpmeslint-scope8.4.0eslint-scope

Change the conditions
Fixed
Package version8.4.0 Symboleslint-scope
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

eslint-scope @8.4.0alpine musl · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27

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