CodeSampleX

Recordsnpm@eslint/config-array0.19.2@eslint/config-array.ConfigArraySymbol

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

Current conditions

@eslint/config-array.ConfigArraySymbol @0.19.2ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

0.19.2

linux · node@22.23 · executionContext=node

2 FAIL · stage: UNKNOWN · fingerprint: sha256:d479d1ac8b042f76ae5ec1fb49e53b5ae3b6fe2e6258b4879b585a3a55ea72c3

Library Version Health Measured there Projects
@eslint/object-schema 2.1.7 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
minimatch 3.1.5 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
debug 4.4.3 PASS All observations passed 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.

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