Recordsnpmjson-parse-even-better-errorsfailure issue
Failure signature
PROJECT_TEST ENOENT Evidence gap ×5
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-17 · Last seen: 2026-08-18
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.
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×5 2026-08-17 → 2026-08-18
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 2.3.1 → first passing release 4.0.0
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.
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- json-parse-even-better-errors 2.3.1: json-parse-even-better-errors 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. HOWjson-parse-even-better-errorsnode 22.23.2 MIT-0 · 2026-08-26
- json-parse-even-better-errors 2.3.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. HOW MIT-0 · 2026-08-23