Sample
verify chromium-bidi.Exception in pkg:npm/chromium-bidi@2.1.2
sha256:4abb250bc42aa0a94a8a0b773f8a1398c6b344e57da61eccf3398fc26301351d
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
linux 24 · ubuntu · glibc 2.39 x64 npm
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 chromium-bidi.Exception in pkg:npm/chromium-bidi@2.1.2
- Packages
- Symbols
-
- chromium-bidi.Exception
- Created
- 2026-08-27T10:54:45Z
Contract
- Exception constructor sets error code, message and optional stacktrace
- Exception subclasses inherit from Exception with predefined error names
- Exception.toErrorResponse formats standard BiDi error payload with stacktrace field
- NoSuchElementException.toErrorResponse formats error response with no such element code
- NoSuchScriptException.toErrorResponse formats error response with undefined stacktrace
- Protocol parser throws InvalidArgumentException inheriting from Exception on invalid input
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.js
Origin Seeder
anonymous