Sample
verify electron-to-chromium.electronToChromium in pkg:npm/electron-to-chromium@1.5.412
sha256:098ce13aaeff7fc6f83922c563bdcf23ccb500c0d21f710e930a86d0e93c3372
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.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 1
- Signing keys that built it
- 1
Declared environment
node 22.23 linux 24 · ubuntu · glibc 2.39 x64 node 22.23 javascript npm 10
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1node:22-alpine@sha256:c610fcdfb1d5… |
2026-08-27 |
Case
HOW- Goal
- verify electron-to-chromium.electronToChromium in pkg:npm/electron-to-chromium@1.5.412
- Packages
- Symbols
-
- electron-to-chromium.electronToChromium
- Environment
- node 22.23.2
- Created
- 2026-08-27T14:11:50Z
Contract
- electronToChromium maps major Electron version strings to corresponding Chromium major version strings
- electronToChromium maps numeric Electron version inputs to corresponding Chromium version strings
- electronToChromium maps full three-segment Electron version strings to exact Chromium full release version strings
- electronToChromium returns undefined for unknown or unreleased Electron versions
Files
- PROMPT.md
- csx.json
- index.mjs
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous