Recordsnpmcacache
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
16.1.3
linux · node@22.23 · executionContext=node · moduleSystem=cjs
12 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
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 | 20.0.4 | 20.0.3 | 19.0.1 | 16.1.3 |
|---|---|---|---|---|
| @npmcli/fs | 5.0.0 | 5.0.0 | 4.0.0 | 2.1.2 |
| fs-minipass | 3.0.3 | 3.0.3 | 3.0.3 | 2.1.0 |
| glob | 13.0.6 | 13.0.0 | 10.5.0 | 8.1.0 |
| lru-cache | 11.5.1 | 11.2.4 | 10.4.3 | 7.18.3 |
| minipass | 7.1.3 | 7.1.2 | 7.1.3 | 3.3.6 |
| minipass-collect | 2.0.1 | 2.0.1 | 2.0.1 | 1.0.2 |
| minipass-flush | 1.0.6 | 1.0.5 | 1.0.5 | 1.0.7 |
| p-map | 7.0.4 | 7.0.4 | 7.0.4 | 4.0.0 |
| ssri | 13.0.1 | 13.0.0 | 12.0.0 | 9.0.1 |
| tar | — | — | 7.5.22 | 6.2.1 |
| unique-filename | — | 5.0.0 | 4.0.0 | 2.0.1 |
| @npmcli/move-file | — | — | — | 2.0.1 |
| chownr | — | — | — | 2.0.0 |
| infer-owner | — | — | — | 1.0.4 |
| minipass-pipeline | 1.2.4 | 1.2.4 | 1.2.4 | 1.2.4 |
| mkdirp | — | — | — | 1.0.4 |
| promise-inflight | — | — | — | 1.0.1 |
| rimraf | — | — | — | 3.0.2 |
Moved: 11 · 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.