← Index01 / 05 · Verik

Independent verification for agent-written codeTypeScript / Node.js / Git internals2026

Verik

Your agent says it is done. Verik tells you what it actually did.

View repository ↗

Verik project cover — Open-source productDesigned + built by Aymen Bowran

01 / Why this existsGenerator ≠ verifier

A green build is useful. It is not proof the change is safe.

I built Verik for the gap that appears when an agent writes the code and then reports that it worked. It captures the repository before and after, isolates the agent’s edits from work already in progress, runs the project’s own checks plus deterministic rules, and returns an exit code CI can enforce.

02 / Actual verification runverik verify / full pipeline

A real Verik verification run blocking unsafe agent-written changes — Actual terminal outputScout → Builder → Reviewer → Judge

The tests passed. That is the point.

03 / Attribution first

Judge the agent’s work.
Not the mess already on your desk.

BEFORE

Verik capturing the repository before an agent run

Snapshot the working tree

Your unfinished changes are captured as the starting context.

→

RUN

An agent working inside a repository monitored by Verik

Let the agent work

Wrapped command or a named baseline. Vendor does not matter.

→

AFTER

Verik capturing the repository after the agent run

Snapshot it again

A second real git tree records the resulting repository.

→

DIFF

Verik isolating and verifying only the agent-authored changes

Verify only the delta

No stage, stash, commit or checkout touches the repository.

23Deterministic checks

222Repository tests

11Model providers

Next projectSovereign AI infrastructureKastral↗