Recordsnpm@typescript-eslint/parser8.67.0@typescript-eslint/parser.parseForESLint
Change the conditions
Current conditions
@typescript-eslint/parser.parseForESLint @8.67.0ubuntu glibc · x64 · node 22 · npm 10 · node
0 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 failed (1)
- Project observations
- 1 / 1
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.67.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:2baa184da33684e683416412474a6ac55636b5e3717a55cfedb90792ff17378c
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @typescript-eslint/scope-manager | 8.67.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| @typescript-eslint/types | 8.67.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| @typescript-eslint/typescript-estree | 8.67.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| @typescript-eslint/visitor-keys | 8.67.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| debug | 4.4.3 | PASS All observations passed | contract passed | 1 project-day |
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/scope-manager | 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/typescript-estree | 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 |
| debug | 4.4.3 | 4.4.3 | 4.4.3 | 4.4.3 | 4.4.3 | 4.4.3 |
Moved: 4 · 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
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 8.67.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 @typescript-eslint/parser.parseForESLint sha256:2baa184da336…node:internal/assert/utils:<n> · throw err; · ^ · AssertionError [ERR_ASSERTION]: Global scope should record variable alphanode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate