Recordsnpmreusifyfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-20 · Last seen: 2026-08-20
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.
- 1.1.0 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-08-20 → 2026-08-20
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.
- No release in this window recorded a passing observation at PROJECT_PROCESS.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- reusify 1.1.0: reusify 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. HOWreusifynode 22.23.2 MIT-0 · 2026-09-01
- reusify 1.1.0 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-08-28
- reusify 1.1.0 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-08-20