CodeSampleX

Recordsnpm@eslint/eslintrc3.3.6Legacy.ConfigArray

Change the conditions
Fixed
Package version3.3.6 SymbolLegacy.ConfigArray
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

Legacy.ConfigArray @3.3.6alpine 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-28

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 4

First observed break

3.3.6

windows · node@24.13 · executionContext=node · moduleSystem=esm

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

Library Version Health Measured there Projects
ajv 6.15.0 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
espree 10.4.0 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
globals 14.0.0 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
js-yaml 4.3.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
js-yaml 4.3.1 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
js-yaml 4.3.2 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
minimatch 3.1.5 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
debug 4.4.3 PASS All observations passed contract passed 17 project-days
ignore 5.3.2 PASS All observations passed contract passed 17 project-days
import-fresh 3.3.1 PASS All observations passed contract passed 17 project-days
strip-json-comments 3.1.1 PASS All observations passed contract passed 16 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: 5 · 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

Showing the 12 most-reported of 27 recorded failure clusters. The rest are single reports.