Recordsnpm@xmldom/xmldomfailure issue
Failure signature
PROJECT_TEST exit 1 EOF ×1
[31m[1mAssertionError[22m: expected [ <str>, <str>, <str>, <str> ] to deeply equal [ <str>, <str>, <str>, <str> ][39m · [32m- Expected[39m …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:d757efcbaf88…
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.
- 0.9.12 PASS 1 passing observations
- 0.9.10 FAIL
- 0.8.15 not measured
- 0.8.14 PASS 62 passing observations
- 0.8.13 PASS 170 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-14 → 2026-09-14
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 0.8.14 → first failing release 0.9.10
Releases between them never measured at this stage: 1
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 0.9.10 → first passing release 0.9.12
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No resolved dependency tree for 0.9.12 or for 0.9.10, 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
- @xmldom/xmldom 0.9.10 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-27