CodeSampleX

Recordsnpmelectron33.4.11electron.contextBridge

Change the conditions
Fixed
Package version33.4.11 Symbolelectron.contextBridge Package managernpm 11
Filter OSwindows 11 Runtimenode 24 Architecturex64 Execution contextnode Clear filters

Current conditions

electron.contextBridge @33.4.11windows 11 · x64 · node 24 · npm 11 · node

0 of 12 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
37 / 40
Contract verifications
0 / 12
Independent reporting peers
1
Failures with a captured fingerprint
1 / 3
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

33.4.11

windows · executionContext=node

8 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
@electron/get 2.0.3 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
@types/node 20.19.43 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
extract-zip 2.0.1 PASS All observations passed contract passed 9 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