CodeSampleX

Recordsnpm@typescript-eslint/eslint-plugin8.65.0

Change the conditions
Fixed
OSdebian glibc Symbolwhole package
Filter Runtimenode 22 Package version8.65.0 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

@typescript-eslint/eslint-plugin @8.65.0debian glibc · x64 · node 22 · npm · node

package-level total, not an API

4 of 4 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 (5)

Project observations
16 / 16
Contract verifications
4 / 4
Usage records
9
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 2

First observed break

8.65.0

windows · executionContext=node

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
@typescript-eslint/scope-manager 8.65.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
@typescript-eslint/type-utils 8.65.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
@typescript-eslint/utils 8.65.0 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
@typescript-eslint/visitor-keys 8.65.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
ignore 7.0.6 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
ignore 7.0.8 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
ts-api-utils 2.5.0 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
@eslint-community/regexpp 4.12.2 PASS All observations passed contract passed 15 project-days
natural-compare 1.4.0 PASS All observations passed contract passed 12 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.

Library8.66.08.65.08.46.4
@typescript-eslint/scope-manager 8.66.0 8.65.0 8.46.4
@typescript-eslint/type-utils 8.66.0 8.65.0 8.46.4
@typescript-eslint/utils 8.66.0 8.65.0 8.46.4
@typescript-eslint/visitor-keys 8.66.0 8.65.0 8.46.4
ignore 7.0.6 7.0.6 7.0.5
ts-api-utils 2.5.0 2.5.0 2.1.0
@eslint-community/regexpp 4.12.2 4.12.2 4.12.2
graphemer — — 1.4.0
natural-compare 1.4.0 1.4.0 1.4.0

Moved: 6 · unchanged at every release: 3

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