Recordsnpmeslint-scope5.1.1ScopeManager
Change the conditions
Current conditions
ScopeManager @5.1.1alpine musl · 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 (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-27
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.1.1
windows · node@24.13 · executionContext=node · moduleSystem=cjs
8 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| estraverse | 4.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| esrecurse | 4.3.0 | PASS All observations passed | contract passed | 3 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 | 9.1.2 | 8.4.0 | 7.2.2 | 5.1.1 |
|---|---|---|---|---|
| estraverse | 5.3.0 | 5.3.0 | 5.3.0 | 4.3.0 |
| @types/esrecurse | 4.3.1 | — | — | — |
| @types/estree | 1.0.9 | — | — | — |
| esrecurse | 4.3.0 | 4.3.0 | 4.3.0 | 4.3.0 |
Moved: 1 · unchanged at every release: 3
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.