Recordsnpm@rollup/rollup-linux-x64-gnufailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×5
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-27 · Last seen: 2026-08-30
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.63.2 PASS 14 passing observations
- 4.63.1 PASS 77 passing observations
- 4.63.0 PASS 31 passing observations
- 4.62.5 FAIL
- 4.62.4 PASS 22 passing observations
- 4.62.3 not measured
- 4.54.0 PASS 11 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×5 2026-08-27 → 2026-08-30
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.62.5
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release 4.62.5 → first passing release 4.63.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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_PROCESS: 1
- No resolved dependency tree for 4.62.4 or for 4.62.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
- @rollup/rollup-linux-x64-gnu 4.62.5 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-21