CodeSampleX

Recordsnpm@eslint/plugin-kit0.4.1@eslint/plugin-kit.VisitNodeStep

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

Current conditions

@eslint/plugin-kit.VisitNodeStep @0.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

2 of 2 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-06
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.4.1

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

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

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