Detect without guessing
Committed runtime declarations, locks, manifests, and unique framework entry points define the plan. README commands never auto-run.
DETERMINISTIC LOCAL RUN VERIFICATION
Select a trusted but unfamiliar repository. Verity traces the command evidence, runs an isolated snapshot, and signs a local receipt only after the real machine oracle passes.
Free · no login · local core under MPL-2.0
node-web / windows-x64ONE BOUNDED JOB
Committed runtime declarations, locks, manifests, and unique framework entry points define the plan. README commands never auto-run.
Verity fingerprints the current files, rejects escaping symlinks, acquires dependencies with consent, then removes network access for build and test.
Tests, declared health checks, browser behavior, or checked-in smoke automation decide the result. A process or window alone stays unverified.
SUPPORTED TARGETS
Every receipt covers only the host and execution environment it records. Public support remains gated on the real-project platform matrix.
SECURITY & LIMITS
Trusted source only. Verity is not a hostile-code sandbox. Native stages are isolated snapshots with process controls, not a malware boundary.
Zero guess-passes. Missing locks, ambiguous commands, snapshot changes, incomplete runtimes, and weak oracles stop the run.
Local signature only. A receipt is tamper-evident for this installation. It is not remote certification by Verity.
No upload interface. Raw receipts, repository paths, logs, source, and command output remain on the current machine.
OPEN LOCAL CORE
Desktop app, CLI, adapters, runner, and receipt logic are MPL-2.0. A future team control plane is separate and never required for local verification; raw receipts and run output stay local.
Read the implementation ↗No waitlist account and no misleading download button. Follow the source or review current acceptance status.