CodeSampleX

Recordsnpm@eslint/core0.17.0

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

Current conditions

@eslint/core @0.17.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 5 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
16 / 16
Contract verifications
0 / 5
Usage records
3
Independent reporting peers
2
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

0.17.0

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
@types/json-schema 7.0.15 PASS All observations passed contract passed 20 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.

Library1.2.10.17.00.13.00.11.0
@types/json-schema 7.0.15 7.0.15 7.0.15 7.0.15

Moved: 0 · 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