CodeSampleX

Recordsnpm@eslint/plugin-kit0.7.2

Change the conditions
Fixed
OSalpine musl Package version0.7.2 Package managernpm
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

@eslint/plugin-kit @0.7.2alpine musl · x64 · node 22 · npm · node

package-level total, not an API

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-30
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
@eslint/core 1.2.1 contract passed 7 project-days
levn 0.4.1 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.

Library0.7.20.4.10.2.8
@eslint/core 1.2.1 0.17.0 0.13.0
levn 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