CodeSampleX

Recordsnpmfast-xml-parser5.11.0fast-xml-parser.XMLParser

Change the conditions
Fixed
Runtimenode 22 Symbolfast-xml-parser.XMLParser Package managernpm 11
Filter OSwindows 11 Package version5.11.0 Architecturex64 Execution contextnode Clear filters

Current conditions

fast-xml-parser.XMLParser @5.11.0windows 11 · x64 · node 22 · npm 11 · node

30 of 32 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

Project observations
30 / 32
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-24
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 6

First observed break

5.11.0

windows · node@24.13 · moduleSystem=cjs · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:3e5f03903e292d9b19daef82b234201615ab763216b97feec6f325b598b3380d

View exact conditions View failure cluster
Library Version Health Measured there Projects
strnum 2.4.2 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
@nodable/entities 3.0.0 PASS All observations passed contract passed 5 project-days
fast-xml-builder 1.3.1 PASS All observations passed contract passed 5 project-days
is-unsafe 2.0.0 PASS All observations passed contract passed 4 project-days
is-unsafe 2.0.2 PASS All observations passed contract passed 1 project-day
path-expression-matcher 1.6.2 PASS All observations passed contract passed 5 project-days
xml-naming 0.3.0 PASS All observations passed contract passed 5 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.

Library5.11.05.2.5
strnum 2.4.2 2.1.2
@nodable/entities 3.0.0 —
fast-xml-builder 1.3.1 —
is-unsafe 2.0.2 —
path-expression-matcher 1.6.2 —
xml-naming 0.3.0 —

Moved: 1 · unchanged at every release: 5

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.

Recent failure clusters