Recordsnpmelectron-to-chromium1.5.408
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 1✓
|
LOW | 2 +1 | 1 | 100% | 1 · 1✓ | 2026-08-30 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 3✓
|
LOW | 3 | 0 | 100% | 1 | 2026-08-18 |
| node 24.13 · JS · npm · windows
Observations: PROJECT_PROCESS 31✓ · PROJECT_TEST 1✓ — Usage: USED 1✓
|
LOW | 32 +1 | 0 | 100% | 1 | 2026-08-18 |
Symbols
No symbols with evidence yet.
Published samples
- electron-to-chromium 1.5.408 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-20