CodeSampleX

Recordsnpm@typescript-eslint/project-service8.69.0createProjectService

Change the conditions
Fixed
SymbolcreateProjectService Package managernpm
Filter OSdebian glibc Runtimenode 22 Package version8.69.0 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

createProjectService @8.69.0debian glibc · x64 · node 22 · npm · node

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

Project observations
4 / 4
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-10

Dependency Health

Observed combinations and failure evidence for this release

Changed 6 · Steady 1

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

Library Version Health Measured there Projects
@typescript-eslint/tsconfig-utils 8.69.0 CHANGED Version changed, no linked failure contract passed 10 project-days
@typescript-eslint/tsconfig-utils 8.70.0 CHANGED Version changed, no linked failure builds observed 2 project-days
@typescript-eslint/tsconfig-utils 8.71.1 CHANGED Version changed, no linked failure builds observed 4 project-days
@typescript-eslint/types 8.69.0 CHANGED Version changed, no linked failure contract passed 10 project-days
@typescript-eslint/types 8.70.0 CHANGED Version changed, no linked failure builds observed 2 project-days
@typescript-eslint/types 8.71.1 CHANGED Version changed, no linked failure builds observed 4 project-days
debug 4.4.3 PASS All observations passed contract passed 15 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.

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.