Records/npm/electron-to-chromium/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 1.5.415 PASS 86 passing observations
• 1.5.414 PASS 1 passing observations
• 1.5.413 PASS 1 passing observations
• 1.5.412 FAIL
• 1.5.411 FAIL
• 1.5.408 PASS 34 passing observations
• 1.5.403 FAIL
• 1.5.402 PASS 3 passing observations
• 1.5.400 not measured

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×8 2026-08-20 → 2026-08-27
• executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×5 2026-08-21 → 2026-08-23

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 1.5.402 → first failing release 1.5.403

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last failing release 1.5.403 → first passing release 1.5.408

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last passing release 1.5.408 → first failing release 1.5.411

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last failing release 1.5.412 → first passing release 1.5.413

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_PROCESS: 1
• No resolved dependency tree for 1.5.408 or for 1.5.403, so the versions either side of the boundary could not be compared.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• electron-to-chromium 1.5.412: versions Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWelectron-to-chromium.versionsnode 22.23.2 MIT-0 · 2026-08-27
• electron-to-chromium 1.5.412: fullVersions Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWelectron-to-chromium.fullVersionsnode 22.23.2 MIT-0 · 2026-08-27
• electron-to-chromium 1.5.412: fullChromiumVersions Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWelectron-to-chromium.fullChromiumVersionsnode 22.23.2 MIT-0 · 2026-08-27
• electron-to-chromium 1.5.411: versions Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWelectron-to-chromium.versionsnode 22.23.2 MIT-0 · 2026-09-17
• electron-to-chromium 1.5.411: fullVersions Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWelectron-to-chromium.fullVersionsnode 22.23.2 MIT-0 · 2026-09-17
• electron-to-chromium 1.5.411: fullChromiumVersions Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWelectron-to-chromium.fullChromiumVersionsnode 22.23.2 MIT-0 · 2026-09-17