Recordsnpmrollupfailure issue
Failure signature
PROJECT_COMPILE Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-11-18 · Last seen: 2026-11-18
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.67.5 FAIL
- 4.63.3 not measured
- 4.63.2 not measured
- 4.63.1 not measured
- 4.62.4 PASS 179 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-11-18 → 2026-11-18
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 4.62.4 → first failing release 4.67.5
Releases between them never measured at this stage: 5
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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.62.4 |
|---|---|---|---|---|
| @types/estree | 1.0.9 | 1.0.9 | 1.0.9 | 1.0.9 |
Moved: 0 · 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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- Releases in this window never measured at PROJECT_COMPILE: 3
- No resolved dependency tree for 4.62.4 or for 4.67.5, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.