Recordsnpm@electron/notarize2.5.0@electron/notarize.notarize
Change the conditions
Current conditions
@electron/notarize.notarize @2.5.0debian glibc · x64 · node 22 · npm · 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 (2)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 3
First observed break
2.5.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| debug | 4.4.3 | PASS All observations passed | contract passed | 31 project-days |
| fs-extra | 9.1.0 | PASS All observations passed | contract passed | 31 project-days |
| promise-retry | 2.0.1 | PASS All observations passed | contract passed | 31 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.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×1 2.5.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:795cbb5ee086…Error: Cannot find module <str> · Require stack: · - <path> · - <path>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate