Recordsnpm@standard-schema/specfailure issue
Failure signature
PROJECT_TEST exit 1 ×2
[31m[1mAssertionError[22m: expected [ { kind: <str>, …(2) } ] to deeply equal [][39m · [32m- Expected[39m · [31m+ Received[39m · [32m- [][39m
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-09 · Last seen: 2026-09-09
sha256:87a2d9024768…
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=cjs · os=windows · runtime=node@24.13 ×2 2026-09-09 → 2026-09-09
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
- 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.