CodeSampleX

Recordsnpm@eslint/config-array0.23.5

Change the conditions
Fixed
Package version0.23.5 Symbolwhole package Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@eslint/config-array @0.23.5ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 6 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
24 / 25
Contract verifications
0 / 6
Usage records
1
Independent reporting peers
2
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-31
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
@eslint/object-schema 3.0.5 contract passed 7 project-days
debug 4.4.3 contract passed 8 project-days
minimatch 10.2.6 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.

Library0.23.50.21.20.19.2
@eslint/object-schema 3.0.5 2.1.7 2.1.7
minimatch 10.2.6 3.1.5 3.1.5
debug 4.4.3 4.4.3 4.4.3

Moved: 2 · unchanged at every release: 1

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