Sample
zod 4.4.3: z.ZodType.safeParse
Verified sample for npm zod 4.4.3: z.ZodType.safeParse. The contract ran on node 22 · linux alpine/x64 · docker and passed: safeParse returns success true…
sha256:0a074abe81d160fe06761ccce64928528ddf19f33d345669da8e1bfc7833686a
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
node windows 11 x64 node javascript npm
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 z.ZodType.safeParse in pkg:npm/zod@4.4.3
- Packages
- Symbols
-
- z.ZodType.safeParse
- Environment
- node
- Created
- 2026-08-19T09:07:19Z
Contract
- safeParse returns success true with parsed data for valid string schema
- safeParse returns success false with error details for invalid string schema
- safeParse validates object schemas with required and optional fields successfully
- safeParse fails when object schemas receive invalid field types
- safeParse handles custom refinement validations correctly
Files
- PROMPT.md
- csx.json
- index.js
- package-lock.json
- package.json
- spec.json
- test/contract.js
Origin Seeder
anonymous