jevbooks

← All projects

jev-crawlers

Thingscorp/jev-crawlers

Jev learns repo decision norms, adversarially judges past decisions.

Evaluation & Benchmarking0.96Runner-up: Verification & GuardrailsFunnel
Automated README summary

Automatically summarized from the README on 7 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

A set of Unix-style tools for bug discovery in a repository. They follow leads (callers, co-changed files, config) and use Jev to judge each node, producing evidence-backed findings for developers.

How it uses Jev

jev-judge makes one Jev call per node, asking for a verdict suggestion (expand, report, prune, escalate), a bug_likely ranking signal, a risk score 0-3, and whether a falsifiable artifact is stated. Routing follows risk bands; results are used in the pipeline to decide expansion, reporting, or pruning.

Primitives:choicescorenoul

Technique worth stealing

Cheap per-node typed judgments enable judging every node instead of every scan.

Try it

npm install && ./bin/crawl --repo ./examples/todo-app --dry-run --budget 8

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectFound in material0.86
  • Shows a System One patternFound in material0.62
  • Describes handling uncertaintynot found in the excerpt0.05
  • Reports measured numbersnot found in the excerpt0.05
  • Is a runnable toolFound in material0.78
  • Top-10 learning shortlist signalunclear0.44
  • Is a replica of the modelnot found in the excerpt0.07
  • Solves a common problem (0–2)score on a 0–2 scale1.88 / 2
  • About JevFound in material0.97
Signals
Jev is core to the project0.86Shows a System One pattern0.62Describes handling uncertainty0.05Reports measured numbers0.05Is a runnable tool0.78Top-10 learning shortlist signal0.44Is a replica of the model0.0700.51Solves a common problem (0–2)1.88 / 2012

no-judgment band (0.40–0.60)

Design patterns
Funnel0.83Traffic light0.59Inspection0.52Flight recorder0.5100.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 7 Oct 2026.