Recordsnpmpacote
there is a sample for this release and API (1)
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
Dependency changes observed: 15. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @npmcli/git | 6.0.3 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| @npmcli/installed-package-contents | 3.0.0 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| @npmcli/package-json | 6.2.0 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| @npmcli/promise-spawn | 8.0.3 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| @npmcli/run-script | 9.1.0 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| cacache | 19.0.1 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| minipass | 7.1.3 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| npm-package-arg | 12.0.2 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| npm-packlist | 9.0.0 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| npm-pick-manifest | 10.0.0 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| npm-registry-fetch | 18.0.2 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| proc-log | 5.0.0 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| sigstore | 3.1.0 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| ssri | 12.0.0 | CHANGED Version changed, no linked failure | contract passed | 7 project-days |
| tar | 7.5.22 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| fs-minipass | 3.0.3 | PASS All observations passed | contract passed | 7 project-days |
| promise-retry | 2.0.1 | PASS All observations passed | contract passed | 7 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.
Moved: 15 · 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.