Recordsnpmapp-builder-lib
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
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
26.15.3
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @electron/osx-sign | 1.3.3 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| @electron/rebuild | 4.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| @electron/universal | 2.0.3 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| builder-util | 26.15.3 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| builder-util-runtime | 9.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| electron-publish | 26.15.3 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| js-yaml | 4.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| js-yaml | 4.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| semver | 7.7.4 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| tar | 7.5.22 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| @electron/asar | 3.4.1 | PASS All observations passed | contract passed | 11 project-days |
| @electron/fuses | 1.8.0 | PASS All observations passed | contract passed | 11 project-days |
| @electron/get | 3.1.0 | PASS All observations passed | contract passed | 10 project-days |
| @electron/notarize | 2.5.0 | PASS All observations passed | contract passed | 10 project-days |
| @malept/flatpak-bundler | 0.4.0 | PASS All observations passed | contract passed | 5 project-days |
| @noble/hashes | 2.2.0 | PASS All observations passed | contract passed | 6 project-days |
| @noble/hashes | 2.3.0 | PASS All observations passed | contract passed | 5 project-days |
| @peculiar/webcrypto | 1.7.1 | PASS All observations passed | contract passed | 10 project-days |
| @types/fs-extra | 9.0.13 | PASS All observations passed | contract passed | 10 project-days |
| ajv | 8.20.0 | PASS All observations passed | contract passed | 12 project-days |
| asn1js | 3.0.10 | PASS All observations passed | contract passed | 9 project-days |
| async-exit-hook | 2.0.1 | PASS All observations passed | contract passed | 9 project-days |
| chromium-pickle-js | 0.2.0 | PASS All observations passed | contract passed | 8 project-days |
| ci-info | 4.3.1 | PASS All observations passed | contract passed | 9 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 9 project-days |
| dotenv | 16.6.1 | PASS All observations passed | contract passed | 8 project-days |
| dotenv-expand | 11.0.7 | PASS All observations passed | contract passed | 9 project-days |
| ejs | 3.1.10 | PASS All observations passed | contract passed | 9 project-days |
| fs-extra | 10.1.0 | PASS All observations passed | contract passed | 9 project-days |
| hosted-git-info | 4.1.0 | PASS All observations passed | contract passed | 9 project-days |
| isbinaryfile | 5.0.7 | PASS All observations passed | contract passed | 9 project-days |
| jiti | 2.7.0 | PASS All observations passed | contract passed | 8 project-days |
| json5 | 2.2.3 | PASS All observations passed | contract passed | 9 project-days |
| lazy-val | 1.0.5 | PASS All observations passed | contract passed | 9 project-days |
| minimatch | 10.2.6 | PASS All observations passed | contract passed | 9 project-days |
| pkijs | 3.4.0 | PASS All observations passed | contract passed | 9 project-days |
| plist | 3.1.0 | PASS All observations passed | contract passed | 9 project-days |
| proper-lockfile | 4.1.2 | PASS All observations passed | contract passed | 9 project-days |
| resedit | 1.7.2 | PASS All observations passed | contract passed | 9 project-days |
| temp-file | 3.4.0 | PASS All observations passed | contract passed | 9 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: 9 · unchanged at every release: 38 Longer lists are cut here; the counts above cover all of them.
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.