CodeSampleX

Recordsnpm@eslint/plugin-kit0.7.3@eslint/plugin-kit.Directive

Change the conditions
Fixed
Package version0.7.3 Symbol@eslint/plugin-kit.Directive
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@eslint/plugin-kit.Directive @0.7.3ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 3 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
3 / 3
Contract verifications
0 / 3
Independent reporting peers
2
Last recorded
2026-09-05
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

0.7.3

linux · node@22.23 · executionContext=node

4 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

View exact conditions View failure cluster
Library Version Health Measured there Projects
@eslint/core 1.2.1 CANDIDATE Correlated change; unproven combination contract passed 64 project-days
levn 0.4.1 PASS All observations passed contract passed 64 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.7.30.7.20.4.10.2.8
@eslint/core 1.2.1 1.2.1 0.17.0 0.13.0
levn 0.4.1 0.4.1 0.4.1 0.4.1

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