Recordsnpmproxy-addrfailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×1
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · 0 !== 1 · at TestContext.<anonymous> (<url>) …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-17 · Last seen: 2026-09-17
sha256:e5d62c8db895…
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 ×1 2026-09-17 → 2026-09-17
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 2.0.7 → first failing release 2.0.8
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 0 · unchanged at every release: 2
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.