CodeSampleX

Recordsnpmelectron38.8.6electron.WebContents

Change the conditions
Fixed
Symbolelectron.WebContents Package managernpm
Filter OSalpine musl Runtimenode 22 Package version38.8.6 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

electron.WebContents @38.8.6alpine musl · 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 (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

38.8.6

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

47 FAIL · stage: UNKNOWN · fingerprint: sha256:979755e6489d54fbc02ff712a1ad44c541d0fea0a79afc307d5bbd18aef3107a

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