Recordsnpmfast-xml-parser
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.11.0
windows · node@24.13 · moduleSystem=cjs · executionContext=node
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:3e5f03903e292d9b19daef82b234201615ab763216b97feec6f325b598b3380d
| 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.
| Library | 5.11.0 | 5.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.