Recordsnpmzodfailure issue
Failure signature
PROJECT_TEST ENOENT Evidence gap ×4
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-17 · Last seen: 2026-08-25
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.
- 4.4.3 PASS 71 passing observations
- 4.1.12 PASS 6 passing observations
- 3.25.76 FAIL
- 3.24.2 PASS 3 passing observations
- 3.24.0 PASS 3 passing observations
- 3.23.8 FAIL
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-17 → 2026-08-18
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-25 → 2026-08-25
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 failing release 3.23.8 → first passing release 3.24.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 3.24.2 → first failing release 3.25.76
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 3.25.76 → first passing release 4.1.12
Both trees resolved every dependency to the same version. Nothing here moved.
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 failure domain was inferred for this failure.
Published answers for the affected releases
- zod 3.25.76: z 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. HOWzod.z MIT-0 · 2026-08-28
- zod 3.25.76: Validate recursive tree structures and dynamic key records using z.lazy and z.record in Zod 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. HOWzod.z.lazy MIT-0 · 2026-08-23
- zod 3.25.76 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-19
- zod 3.23.8: z.lazy, z.preprocess, z.pipeline 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. HOWz.lazyz.preprocessz.pipelineparseAsyncsafeParseAsyncnode 22.23.2 MIT-0 · 2026-08-27
- zod 3.23.8 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-19