Recordsnpmelectron43.4.1
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
| alpine musl | 11 | |
|---|---|---|
| electron.BrowserWindow | 100%35 | |
| electron.app | 100%22 | |
| electron.contextBridge | 100%22 | |
| electron.ipcMain | 100%22 | |
| electron.ipcRenderer | 100%22 | |
| electron.shell | 100%22 |
Showing the environments with the most evidence.
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 2✓
|
LOW | 2 +1 | 2 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 1✓ — Verified: CONTRACT 6✓
|
LOW | 2 +1 | 6 | 100% | 1 · 1✓ | 2026-08-30 |
| node 22.16 · TS · npm · windows
Observations: PROJECT_COMPILE 4✓ · PROJECT_TEST 10✓ · PROJECT_TYPECHECK 2✓ 1✕ — Usage: USED 5✓
|
LOW | 17 +5 | 0 | 94% | 1 | 2026-08-24 |
Recent failure clusters
-
observed PROJECT_TYPECHECK Evidence gap ×2 33.4.11 → 43.4.1 executionContext=node · moduleSystem=cjs · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-19 · Last seen: 2026-08-21Diagnostic re-verification candidate
Symbols
- electron.BrowserWindow 1 1 of 1 runs passed
- electron.app 1 1 of 1 runs passed
- electron.contextBridge 1 1 of 1 runs passed
- electron.ipcMain 1 1 of 1 runs passed
- electron.ipcRenderer 1 1 of 1 runs passed
- electron.session 1 1 of 1 runs passed
- electron.shell 1 1 of 1 runs passed
Published samples
- electron 43.4.1 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. HOWnode 22.23.2 MIT-0 · 2026-08-28