Jev Review

What it does

Jev Review inspects either a current Git diff or the source files beneath a selected directory. It moves through a staged sequence: first screening a risk matrix, then profiling files, selecting evidence, classifying the mechanism, scoring severity, and choosing a specialist review path. The result is saved as structured data and presented in a local dashboard.

What you can reuse

The useful part is the orchestration shape. Broad screening happens before focused judgments, while thresholds and routing policy remain in ordinary TypeScript. Its split between domain types, repository adapters, review workflows, CLI entry points, and dashboard code also provides a legible example of keeping model calls away from presentation logic.

How it fits

The input is a diff or source tree. Jev supplies bounded judgments at several stages; application code decides which evidence advances and how a finding is presented. The repository describes findings as prompts for a reviewer rather than proof that a defect exists.

Setup and compatibility

The documented setup requires Node.js 24 or newer, Git, and a TypeSafe API key. It supports commands for reviewing changes, scanning a codebase, saving results, and opening the local report at 127.0.0.1.

Limitations

The author calls the project experimental. It does not integrate compiler diagnostics, static analyzers, or repository indexing, and this directory has not tested its runtime behavior. Treat every reported finding as an item to investigate.

Sources

Primary source: Jev Review repository.