Recordsnpmrollup4.63.2
Change the conditions
Current conditions
rollup @4.63.2ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 29 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 14 / 14
- Contract verifications
- 0 / 29
- Usage records
- 8
- Independent reporting peers
- 3
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.63.2
executionContext=node
40 FAIL
· stage: PROCESS_START
· fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @types/estree | 1.0.9 | CANDIDATE Correlated change; unproven combination | 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.
| 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.
Recent failure clusters
-
observed PROCESS_START process start failed Evidence gap ×40 4.62.4 → 4.63.0 → 4.63.1 → 4.63.2 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 3 · First recorded: 2026-08-31 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_MODULE_NOT_FOUND Evidence gap ×5 4.63.1 → 4.63.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:88af852f99a8…node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-03 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 4.63.2 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:11ef7cd20d31…<url>]:<n> · import assert from <str>; · ^^^^^^ · <str>, and <str> cannot be used outside of module codenode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate