CodeSampleX

Recordsnpm@typescript-eslint/project-service8.67.0

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

Current conditions

@typescript-eslint/project-service @8.67.0debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

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
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-02
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 1

First observed break

8.67.0

linux · node@22.23 · moduleSystem=cjs · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:d1823b81574d74d92d188e86cb53153cb9e4452a764d12ecfdd5a5257dad8ff5

View exact conditions View failure cluster
Library Version Health Measured there Projects
@typescript-eslint/tsconfig-utils 8.67.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
@typescript-eslint/tsconfig-utils 8.68.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
@typescript-eslint/types 8.67.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
@typescript-eslint/types 8.68.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
debug 4.4.3 PASS All observations passed contract passed 9 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/tsconfig-utils 8.70.0 8.68.0 8.68.0 8.66.0 8.68.0 8.46.4
@typescript-eslint/types 8.70.0 8.68.0 8.68.0 8.66.0 8.68.0 8.46.4
debug 4.4.3 4.4.3 4.4.3 4.4.3 4.4.3 4.4.3

Moved: 2 · 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