Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

The CLI gathers commit metadata and diff evidence, then asks Jev Noul questions about change, bug, and security classifications. It aggregates section judgments into category probabilities and produces filtered HTML or CSV reports; those judgments are review signals, not proof of a vulnerability.

What Jev decides

Does the commit fix a bug?Example answers · not a recorded Jev response · Source ↗
Question 1 · t0 e0 bug
YOUR APP
INSTRUCTION

Does the actual change in reviews[0].diff_sections[0] support that this commit fixes a pre-existing behavioral bug? Judge changed code and before/after differences, not mentions.

STATE

Commit metadata and selected diff evidence are packed under reviews[0], including changed diff sections and file paths.

JEV · NOUL
YesNo

App workflow

  1. Select Git history

    Choose a local directory or repository and bound the scan by count, commit, or date range.

  2. Build diff evidence

    The tool collects commit metadata and source-change sections, applying its review policy.

  3. Classify evidence

    Jev evaluates bounded classification questions over the commit evidence.

  4. Review results

    The CLI saves scans locally and exports or filters reports in HTML or CSV.

Why it is interesting

It applies typed judgments to concrete source changes and retains evidence sections alongside classifications, so reviewers can inspect why a commit was flagged.