CodeSampleX

Recordsnpmelectron33.4.11

Change the conditions
Fixed
Runtimenode 22 Package version33.4.11 Package managernpm 10
Filter OSubuntu glibc Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

electron @33.4.11ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

15 of 15 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (13)

Project observations
15 / 15
Contract verifications
nothing at this coordinate
Usage records
8
Independent reporting peers
3
Last recorded
2026-08-31

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.