CodeSampleX

Recordsnpm@electron/get2.0.3getHostArch

Change the conditions
Fixed
OSubuntu glibc Runtimenode 22 SymbolgetHostArch
Filter Package version2.0.3 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

getHostArch @2.0.3ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 1 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 (2)

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 4

First observed break

2.0.3

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

64 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

Library Version Health Measured there Projects
debug 4.3.7 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
debug 4.4.3 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
env-paths 2.2.1 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
semver 6.3.1 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
fs-extra 8.1.0 PASS All observations passed contract passed 16 project-days
got 11.8.6 PASS All observations passed contract passed 16 project-days
progress 2.0.3 PASS All observations passed contract passed 15 project-days
sumchecker 3.0.1 PASS All observations passed contract passed 12 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: 3 · unchanged at every release: 5

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

Showing the 12 most-reported of 25 recorded failure clusters. The rest are single reports.