Recordsnpmtape
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
5.10.2
linux · node@22.23 · executionContext=node · moduleSystem=cjs
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:7761a9558e8935e97e22ee51cbabcc9265c6251abc26761abb3da1a6ed94a926
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @ljharb/now | 1.0.1 | PASS All observations passed | contract passed | 3 project-days |
| @ljharb/resumer | 0.1.3 | PASS All observations passed | contract passed | 3 project-days |
| @ljharb/through | 2.3.14 | PASS All observations passed | contract passed | 3 project-days |
| array.prototype.every | 1.1.7 | PASS All observations passed | contract passed | 3 project-days |
| call-bind | 1.0.9 | PASS All observations passed | contract passed | 3 project-days |
| call-bound | 1.0.4 | PASS All observations passed | contract passed | 3 project-days |
| deep-equal | 2.2.3 | PASS All observations passed | contract passed | 3 project-days |
| defined | 1.0.1 | PASS All observations passed | contract passed | 2 project-days |
| dotignore | 0.1.2 | PASS All observations passed | contract passed | 2 project-days |
| es-object-atoms | 1.1.2 | PASS All observations passed | contract passed | 3 project-days |
| for-each | 0.3.5 | PASS All observations passed | contract passed | 2 project-days |
| get-package-type | 0.1.0 | PASS All observations passed | contract passed | 2 project-days |
| glob | 7.2.3 | PASS All observations passed | contract passed | 1 project-day |
| has-dynamic-import | 2.1.1 | PASS All observations passed | contract passed | 1 project-day |
| hasown | 2.0.4 | PASS All observations passed | contract passed | 2 project-days |
| inherits | 2.0.4 | PASS All observations passed | contract passed | 1 project-day |
| is-regex | 1.2.1 | PASS All observations passed | contract passed | 3 project-days |
| minimist | 1.2.8 | PASS All observations passed | contract passed | 3 project-days |
| mock-property | 1.1.2 | PASS All observations passed | contract passed | 1 project-day |
| object-inspect | 1.13.4 | PASS All observations passed | contract passed | 2 project-days |
| object-is | 1.1.6 | PASS All observations passed | contract passed | 2 project-days |
| object-keys | 1.1.1 | PASS All observations passed | contract passed | 2 project-days |
| object.assign | 4.1.7 | PASS All observations passed | contract passed | 2 project-days |
| resolve | 2.0.0-next.7 | PASS All observations passed | contract passed | 1 project-day |
| string.prototype.trim | 1.2.11 | PASS All observations passed | contract passed | 2 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.