zod
TypeScript-first schema validation with static type inference
Not yet verifiedsource: GitHubhomepageTypeScriptMITcommit 680d19f7d1e0
TypeScript, MIT licensed. The project labels itself: runtime validation, schema validation, static types, type inference and typescript.
zod has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.
- Exact commit tested
- 680d19f7d1e0
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Install time
- the run did not report one
- Cold machine to finish
- the attempt was stopped at the time limit after 90 minutes, so it never finished
- Errors hit and fixed
- the attempt was cut off at the time limit before it reported what it had hit
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Model tokens used
- not recorded for this run
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Whether it works at all
- the attempt did not get far enough to verify anything before the time limit
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
packages/docs build: ▲ Next.js 15.5.25 (Turbopack) packages/docs build: - Experiments (use with caution): packages/docs build: · turbo packages/docs build: ⨯ turbopackScopeHoisting packages/docs build: packages/docs build: Creating an optimized production build ... packages/docs build: [MDX] update map file: 25.051ms packages/docs build: ⚠ The config property `experimental.turbo` is deprecated. Move this setting t… packages/docs build: exit 143 exit=0 exec /bin/sh -lc 'cd /work/repo && export PATH="$HOME/.nub/bin:$PATH" && nub run --filter=@zod/docs buil…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.22 |
Topics (from GitHub)
runtime-validationschema-validationstatic-typestype-inferencetypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zod)Questions
- Does zod run?
- zod has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test zod?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for zod?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.