CodeSampleX

Compatibilitynpm@eslint/config-helpers0.4.2globalIgnores

Change the conditions
Fixed
OSalpine musl SymbolglobalIgnores Architecturex64
Filter Runtimenode 22 Package version0.4.2 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

globalIgnores @0.4.2alpine 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
@eslint/core 0.17.0 contract passed 2 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.

Library0.7.00.4.2
@eslint/core 1.2.1 0.17.0

Moved: 1 · unchanged at every release: 0

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