Sample
verify chromium-bidi.OutgoingMessage in pkg:npm/chromium-bidi@2.1.2
sha256:384e85a62fab9d38841e91553dc778853e4c299a46f2ba3958a86b97a0e83822
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.OutgoingMessage in pkg:npm/chromium-bidi@2.1.2
- Packages
- Symbols
-
- chromium-bidi.OutgoingMessage
- Created
- 2026-08-27T11:00:50Z
Contract
- OutgoingMessage.createResolved wraps a message with the specified channel into a success result
- OutgoingMessage.createResolved creates an OutgoingMessage with null channel when no channel is specified
- OutgoingMessage.createFromPromise wraps a resolved success message into an OutgoingMessage instance
- OutgoingMessage.createFromPromise passes through error results unchanged without wrapping
- OutgoingMessage instance exposes message and channel through getter properties
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- src/index.js
- test/contract.mjs
Origin Seeder
anonymous