Recordsnpm@electron/get
Change the conditions
Current conditions
@electron/get.initializeProxy @2.0.3x64 · 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
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-21
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.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.0.3
windows · node@24.13 · moduleSystem=esm · executionContext=node
64 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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 | 5.1.0 | 3.1.0 | 2.0.3 |
|---|---|---|---|
| debug | 4.4.3 | 4.4.3 | 4.3.7 |
| env-paths | 3.0.0 | 2.2.1 | 2.2.1 |
| semver | 7.7.4 | 6.3.1 | 6.3.1 |
| fs-extra | — | 8.1.0 | 8.1.0 |
| got | — | 11.8.6 | 11.8.6 |
| graceful-fs | 4.2.11 | — | — |
| progress | 2.0.3 | 2.0.3 | 2.0.3 |
| sumchecker | 3.0.1 | 3.0.1 | 3.0.1 |
Moved: 3 · unchanged at every release: 5
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.