Recordsnpmtar
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| 7.5.22 | 7.5.4 | 6.2.1 | |
|---|---|---|---|
| tar | 94%66 | 100%4 | 99%96 |
| tar.c | 100%4 | ||
| tar.create | 100%2 | 100%2 | |
| tar.extract | 100%2 | 100%2 | |
| tar.t | 100%3 | ||
| tar.x | 100%6 |
Showing the environments with the most evidence.
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.5.22
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 | 7.5.22 | 7.5.4 | 6.2.1 |
|---|---|---|---|
| chownr | 3.0.0 | 3.0.0 | 2.0.0 |
| minipass | 7.1.3 | 7.1.2 | 5.0.0 |
| minizlib | 3.1.0 | 3.1.0 | 2.1.2 |
| yallist | 5.0.0 | 5.0.0 | 4.0.0 |
| @isaacs/fs-minipass | 4.0.1 | 4.0.1 | — |
| fs-minipass | — | — | 2.1.0 |
| mkdirp | — | — | 1.0.4 |
Moved: 4 · unchanged at every release: 3
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.