Records/npm/@xmldom/xmldom/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 0.9.10 PASS 1 passing observations
• 0.8.15 PASS 10 passing observations
• 0.8.14 PASS 28 passing observations
• 0.8.13 FAIL

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-23 → 2026-08-23

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 0.8.13 → first passing release 0.8.14

  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

• @xmldom/xmldom 0.8.13: XMLSerializer Built ? 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@xmldom/xmldom.XMLSerializer MIT-0 · 2026-08-23
• @xmldom/xmldom 0.8.13: DOMParser Built ? 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@xmldom/xmldom.DOMParsernode 22.23.2 MIT-0 · 2026-08-23
• @xmldom/xmldom 0.8.13: DOMImplementation Built ? 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@xmldom/xmldom.DOMImplementation MIT-0 · 2026-08-23