Recordsnpmisarrayfailure issue
Failure signature
PROJECT_TYPECHECK Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-20 · Last seen: 2026-08-21
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TYPECHECK 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@22.16 ×1 2026-08-20 → 2026-08-20
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
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 1.0.0 → first passing release 2.0.5
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
- isarray 1.0.0: isarray 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. HOWisarray MIT-0 · 2026-09-01
- isarray 1.0.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. HOW MIT-0 · 2026-08-28