Recordsnpm@typescript-eslint/project-service
Change the conditions
Current conditions
@typescript-eslint/project-service @8.65.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 (3)
- Project observations
- 4 / 4
- Contract verifications
- 1 / 1
- Usage records
- 9
- Independent reporting peers
- 2
- Last recorded
- 2026-09-16
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
@typescript-eslint/project-service.createProjectService
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.65.0
windows · executionContext=node
5 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @typescript-eslint/tsconfig-utils | 8.65.0 | CANDIDATE Correlated change; unproven combination | contract passed | 66 project-days |
| @typescript-eslint/tsconfig-utils | 8.68.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| @typescript-eslint/tsconfig-utils | 8.69.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| @typescript-eslint/types | 8.65.0 | CANDIDATE Correlated change; unproven combination | contract passed | 66 project-days |
| @typescript-eslint/types | 8.68.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| @typescript-eslint/types | 8.69.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 69 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.
| Library | 8.69.0 | 8.68.0 | 8.67.0 | 8.66.0 | 8.65.0 | 8.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.