Recordsnpm@standard-schema/specfailure issue
Failure signature
PROJECT_TYPECHECK Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-19 · Last seen: 2026-08-19
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-19 → 2026-08-19
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 1.0.0 → first failing release 1.1.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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 resolved dependency tree for 1.0.0 or for 1.1.0, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.