Sample
verify puppeteer.launch in pkg:npm/puppeteer@24.4.0
sha256:14a2119c409fb58acbabbbe5a60799f1d412798a22b91cc13352d045c4829b87
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-23 |
Case
HOW- Goal
- verify puppeteer.launch in pkg:npm/puppeteer@24.4.0
- Packages
- Symbols
-
- puppeteer.launch
- Created
- 2026-08-23T06:49:52Z
Contract
- puppeteer.launch is a function exported on the Puppeteer library
- Calling puppeteer.launch with an unknown browser product rejects with an Unknown product error
- Calling puppeteer.launch with a non-existent executablePath rejects with Browser was not found at the configured executablePath
- Calling puppeteer.launch with an executable that exits immediately rejects with Failed to launch the browser process
- Calling puppeteer.launch without a downloaded browser in offline cache rejects with Could not find Chrome
Files
- PROMPT.md
- csx.json
- index.mjs
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous