Recordsnpm@npmcli/git
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
6.0.3
linux · node@22.23 · moduleSystem=esm · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:536db39a2e089f7ed603954e4a67695a077090ed80e3d0d1ef21bd2d6a9e9b21
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @npmcli/promise-spawn | 8.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 29 project-days |
| ini | 5.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 29 project-days |
| lru-cache | 10.4.3 | CANDIDATE Correlated change; unproven combination | contract passed | 29 project-days |
| npm-pick-manifest | 10.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 29 project-days |
| proc-log | 5.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 29 project-days |
| semver | 7.7.4 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| semver | 7.8.5 | CANDIDATE Correlated change; unproven combination | contract passed | 26 project-days |
| which | 5.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 29 project-days |
| promise-retry | 2.0.1 | PASS All observations passed | contract passed | 29 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 | 7.0.2 | 7.0.1 | 6.0.3 |
|---|---|---|---|
| @npmcli/promise-spawn | 9.0.1 | 9.0.1 | 8.0.3 |
| ini | 6.0.0 | 6.0.0 | 5.0.0 |
| lru-cache | 11.5.1 | 11.2.4 | 10.4.3 |
| npm-pick-manifest | 11.0.3 | 11.0.3 | 10.0.0 |
| proc-log | 6.1.0 | 6.1.0 | 5.0.0 |
| semver | 7.8.5 | 7.7.3 | 7.7.4 |
| which | 6.0.1 | 6.0.0 | 5.0.0 |
| @gar/promise-retry | 1.0.3 | — | — |
| promise-retry | — | 2.0.1 | 2.0.1 |
Moved: 7 · unchanged at every release: 2
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.