Records/npm/universalify/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 2.0.1 FAIL
• 0.2.0 not measured
• 0.1.2 PASS 244 passing observations

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-08-29 → 2026-08-29

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 0.1.2 → first failing release 2.0.1

  Releases between them never measured at this stage: 1

  Both trees resolved every dependency to the same version. Nothing here moved.

Evidence gaps

• Releases in this window never measured at PROJECT_TEST: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• universalify 2.0.1 Built ? 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-21
• universalify 2.0.1: fromPromise Built ? 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. HOWuniversalify.fromPromisenode 22.23.2 MIT-0 · 2026-08-20
• universalify 2.0.1: fromCallback Built ? 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. HOWuniversalify.fromCallbacknode 22.23.2 MIT-0 · 2026-08-20