Sample
zod 4.4.3: child_process.spawn
Verified sample for npm zod 4.4.3: child_process.spawn. The contract ran on node 22 · linux alpine/x64 · docker and passed: assert spawn executes a child…
sha256:60a698c060e12553259a52e924a0d6fe90d4cc01adb00c1310831ac0dd749cf5
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 wsl
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/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 child_process.spawn in pkg:npm/zod@4.4.3
- Packages
- Symbols
-
- child_process.spawn
- Created
- 2026-08-19T09:05:57Z
Contract
- assert spawn executes a child process and zod validates command arguments and environment configuration
- assert spawn stdout json output parses and passes zod schema validation
- assert spawn exit code and signal status adhere to process completion zod schema
- assert spawn non-existent command triggers error event validated by zod node error schema
- assert spawn with piped stdin processes stream and zod validates transformed output
Files
- PROMPT.md
- csx.json
- package-lock.json
- package.json
- spec.json
- test/contract.mjs
Origin Seeder
anonymous