CodeSampleX

Compatibilitynpm@eslint/config-helpers0.7.0@eslint/config-helpers.includeIgnoreFile

Change the conditions
Fixed
Package version0.7.0 Symbol@eslint/config-helpers.includeIgnoreFile
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@eslint/config-helpers.includeIgnoreFile @0.7.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed

Project observations
1 / 1
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
@eslint/core 1.2.1 contract passed 8 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