CodeSampleX

Recordsnpm@eslint/plugin-kit0.2.8

Change the conditions
Fixed
Runtimenode 24 Package version0.2.8 Symbolwhole package
Filter OSwindows 11 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@eslint/plugin-kit @0.2.8windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

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 (2)

Project observations
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-17

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 1

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
@eslint/core 0.13.0 CHANGED Version changed, no linked failure contract passed 5 project-days
levn 0.4.1 PASS All observations passed contract passed 5 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.