Recordsnpmadm-zipfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
> capturepack@0.5.1 check:site · > node <path> · Landing translations · PASS en: 42 rendered strings
Evidence quality: complete · npm · unclassified-diagnostic · outer npm run · gap stage-unknown · First recorded: 2026-09-16 · Last seen: 2026-09-16
sha256:a0a8ceaaf237…
adm-zip.IZipEntry
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-16 → 2026-09-16
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- adm-zip 0.6.1 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. HOWnode 22.23.2 MIT-0 · 2026-09-16