Recordsnpm@electron/asar
Change the conditions
Current conditions
@electron/asar.createPackage @3.4.1x64 · node 22 · node
1 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (1)
- Project observations
- 4 / 4
- Contract verifications
- 1 / 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
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
0 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.4.1
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| commander | 5.1.0 | PASS All observations passed | contract passed | 36 project-days |
| glob | 7.2.3 | PASS All observations passed | contract passed | 35 project-days |
| minimatch | 3.1.5 | PASS All observations passed | contract passed | 35 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.