CodeSampleX

Recordsnpm@typescript-eslint/typescript-estree8.65.0

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

Current conditions

@typescript-eslint/typescript-estree @8.65.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 11 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
25 / 28
Contract verifications
0 / 11
Usage records
47
Independent reporting peers
1
Failures with a captured fingerprint
1 / 3
Last recorded
2026-09-16
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/project-service 8.65.0 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
@typescript-eslint/tsconfig-utils 8.65.0 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
@typescript-eslint/types 8.65.0 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
@typescript-eslint/visitor-keys 8.65.0 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
minimatch 10.2.6 CANDIDATE Correlated change; unproven combination contract passed 64 project-days
semver 7.8.5 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
ts-api-utils 2.5.0 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
debug 4.4.3 PASS All observations passed contract passed 65 project-days
tinyglobby 0.2.17 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.

Library8.69.08.68.08.67.08.66.08.65.08.46.4
@typescript-eslint/project-service 8.69.0 8.68.0 8.67.0 8.66.0 8.65.0 8.46.4
@typescript-eslint/tsconfig-utils 8.69.0 8.68.0 8.67.0 8.66.0 8.65.0 8.46.4
@typescript-eslint/types 8.69.0 8.68.0 8.67.0 8.66.0 8.65.0 8.46.4
@typescript-eslint/visitor-keys 8.69.0 8.68.0 8.67.0 8.66.0 8.65.0 8.46.4
minimatch 10.2.6 10.2.6 10.2.6 10.2.6 10.2.6 9.0.5
semver 7.8.5 7.8.5 7.8.5 7.8.5 7.8.5 7.7.3
ts-api-utils 2.5.0 2.5.0 2.5.0 2.5.0 2.5.0 2.1.0
debug 4.4.3 4.4.3 4.4.3 4.4.3 4.4.3 4.4.3
fast-glob — — — — — 3.3.3
is-glob — — — — — 4.0.3
tinyglobby 0.2.17 0.2.17 0.2.17 0.2.17 0.2.17 —

Moved: 7 · unchanged at every release: 4

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