Sample
puppeteer 24.4.0: page.exposeFunction
Verified sample for npm puppeteer 24.4.0: page.exposeFunction. The contract ran on chrome 134 · linux debian/x64 · docker and passed: page.exposeFunction…
sha256:36db44af78683a40b3d1598ba0c1ed6320a5e086ffd375fafe9206fd199c5f4c
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
chrome 134 linux x64 node 22 javascript npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| chrome 134 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-19 |
Case
HOW- Goal
- verify page.exposeFunction in pkg:npm/puppeteer@24.4.0
- Packages
- Symbols
-
- page.exposeFunction
- Environment
- chrome 134
- Created
- 2026-08-18T13:24:42Z
Contract
- page.exposeFunction exposes a Node.js function onto the browser window object.
- The exposed function returns a Promise inside the page execution context.
- Awaiting the exposed function resolves to the return value of the Node.js handler.
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous