CodeSampleX

Recordsnpm@eslint/core1.2.1

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

Current conditions

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

package-level total, not an API

0 of 8 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
26 / 27
Contract verifications
0 / 8
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
@types/json-schema 7.0.15 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.

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