Recordsnpmrollup4.62.3
Change the conditions
Current conditions
rollup @4.62.3alpine musl · x64 · node 22 · npm · node
package-level total, not an API
2 of 2 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
- 2 / 2
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.62.3
windows · node@24.13 · executionContext=node
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @types/estree | 1.0.9 | CANDIDATE Correlated change; unproven combination | 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 | 4.63.3 | 4.63.2 | 4.63.1 | 4.63.0 | 4.62.5 | 4.62.4 | 4.62.3 | 4.54.0 | 4.34.8 | 4.24.0 |
|---|---|---|---|---|---|---|---|---|---|---|
| @types/estree | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.8 | 1.0.6 | 1.0.6 |
Moved: 1 · unchanged at every release: 0
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.