Recordsnpm@npmcli/package-json
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.0.5 | 7.0.4 | 6.2.0 | |
|---|---|---|---|
| @npmcli/package-json | 100%4 | — | 100%14 |
| @npmcli/package-json.create | 100%1 | ||
| @npmcli/package-json.load | 100%1 | ||
| PackageJson.create | 100%1 | ||
| PackageJson.load | 100%1 | ||
| PackageJson.normalize | 100%1 |
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
6.2.0
linux · node@22.23 · executionContext=node · moduleSystem=esm
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:536db39a2e089f7ed603954e4a67695a077090ed80e3d0d1ef21bd2d6a9e9b21
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: 6 · 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.