Recordsnpmelectron33.4.11electron.ipcRenderer
OS × runtime at a glance
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.
Published samples
- electron 33.4.11: ipcRenderer 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.ipcRenderernode 22.23.2 MIT-0 · 2026-08-26
Compatibility matrix
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
Verified: CONTRACT 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-26 |
| node 24.13 · TS · npm · windows
Observations: PROJECT_COMPILE 2✓ · PROJECT_TEST 4✓ 1✕ · PROJECT_TYPECHECK 2✓ 1✕
|
LOW | 10 | 0 | 80% | 1 | 2026-08-21 |
snapshot · 2026-08-30
Failure clusters
-
observed PROJECT_TEST Evidence gap ×8 33.4.11 → 38.8.6 executionContext=node · os=windows electron.ipcRendererEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate
-
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
-
observed PROJECT_TYPECHECK Evidence gap ×1 33.4.11 executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 electron.ipcRendererEvidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-21 · Last seen: 2026-08-21