Recordsnpmglob
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
7.2.3
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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 | 13.0.6 | 13.0.0 | 10.5.0 | 10.3.10 | 8.1.0 | 7.2.3 |
|---|---|---|---|---|---|---|
| jackspeak | — | — | 3.4.3 | 2.3.6 | — | — |
| minimatch | 10.2.5 | 10.1.1 | 9.0.5 | 9.0.5 | 5.1.9 | 3.1.2 |
| minipass | 7.1.3 | 7.1.2 | 7.1.2 | 7.1.2 | — | — |
| path-scurry | 2.0.2 | 2.0.1 | 1.11.1 | 1.11.1 | — | — |
| foreground-child | — | — | 3.3.1 | 3.3.1 | — | — |
| fs.realpath | — | — | — | — | 1.0.0 | 1.0.0 |
| inflight | — | — | — | — | 1.0.6 | 1.0.6 |
| inherits | — | — | — | — | 2.0.4 | 2.0.4 |
| once | — | — | — | — | 1.4.0 | 1.4.0 |
| package-json-from-dist | — | — | 1.0.1 | — | — | — |
| path-is-absolute | — | — | — | — | — | 1.0.1 |
Moved: 4 · unchanged at every release: 7
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.