CodeSampleX

Recordsnpmelectron43.2.0electron.IpcMainInvokeEvent

Change the conditions
Fixed
Package version43.2.0 Symbolelectron.IpcMainInvokeEvent
Filter OSwindows 11 Runtimenode 24 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

electron.IpcMainInvokeEvent @43.2.0windows 11 · x64 · node 24 · npm 11 · node

0 of 36 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
32 / 38
Contract verifications
0 / 36
Independent reporting peers
1
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

43.2.0

windows · node@24.13 · moduleSystem=cjs · executionContext=node

5 FAIL · stage: UNKNOWN · fingerprint: sha256:bc4d7ddc5bcdb4d412bf4a8bb2673c786c7e3852044dc88acdc3e1dc4e6f49cb

Library Version Health Measured there Projects
@electron/get 5.1.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
@types/node 24.13.3 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
@electron-internal/extract-zip 1.0.5 PASS All observations passed contract passed 6 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: 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.

Recent failure clusters