Recordsnpmelectron
Change the conditions
Current conditions
electron.shell @43.4.1musl · x64 · node 22 · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 22 / 22
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-28
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
windows 11 · x64 · node 22 · npm 11 · node
22 of 22 passed
Observed — real project builds reported from this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @electron-internal/extract-zip | 1.0.5 | contract passed | 3 project-days |
| @electron/get | 5.1.0 | contract passed | 3 project-days |
| @types/node | 24.13.3 | contract passed | 3 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 | 43.4.1 | 38.8.6 | 33.4.11 |
|---|---|---|---|
| @electron/get | 5.1.0 | 2.0.3 | 2.0.3 |
| @types/node | 24.13.3 | 22.20.1 | 20.19.43 |
| @electron-internal/extract-zip | 1.0.5 | — | — |
| extract-zip | — | 2.0.1 | 2.0.1 |
Moved: 2 · 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.