A CLI that scans a codebase's source, config, build and CI files with Jev for hidden or data-stealing behavior, pointing to suspicious files and lines as a second opinion before running unfamiliar code.
Read from GitHub on . Counts change daily.
const response = await client.systemOne(
{
state,
questions,
...(model ? { model } : {}),
},
{ timeout: options.timeout ?? 60_000 },
);The 1,978-point, 513-comment launch thread. The top comment calls the speed comparison misleading, since Jev only returns structured output, and disputes the cannot-hallucinate claim because a valid type can still hold a wrong value. Others note ordinary LLMs can already be forced into structured output.
Guarantees valid structured output during generation by constraining decoding to a grammar or schema. The mechanism HN commenters repeatedly cited as already covering Jev's cannot-produce-a-type-error guarantee on ordinary LLMs. Star count is GitHub's rounded display figure.
Staged code-review workflow with a local dashboard, where Jev judges code changes or a whole codebase.
Places Jev as a fast supervisor above slower Codex coding agents. Codex workers do the engineering while Foreman independently assesses whether the work is complete, requirements are met, tests suffice, or human input is needed.
Extension making Jev the decision layer for the Pi coding agent: a measured tool-call gate plus a jev_ask tool. Judges whether an action is destructive, exfiltrates data or exceeds scope, then blocks or warns on calibrated thresholds.
144 starsGate latency ~300ms
Guardrails for the Pi agent built on pi-typesafe. Jev judges irreversible and off-task tool calls, detects stuck loops, checks unverified completion claims and flags low-quality output, steering the agent rather than interrupting the user.
DevMortimerOpenpi-warden on github.com138 starsHolds per 1000 calls 3
