jev-baselines-eval
ickma2311
Every latency number here is **wall-clock duration of one API call** measured in the client: a timestamp before the request, another after the full response body is read ([`code/run_b1.py:32`](code/run_b1.py), [`code/common.py:50`](code/common.py)). Non-streaming on both sides, so these are completion times, not time-to-first-token.
- License
- MIT
- GitHub Stars
- 4
- Source reviewed
- —
Where Jev makes a decision
Jev returns a structured decision for the local program; consult the source for the exact decision policy.
What this project offers
Adds structured choices or scores to the workflow; performance and cost benefits have not been independently verified.
Review scope
Based on repository metadata and README with rule-based classification; pending human review, with no independent runtime or performance verification.
Sources and implementation
Related projects
safer-with-jev
andrelandgraf · Security & Guardrails
An HTTP inspection gateway that checks request content with Jev before optionally forwarding it to an HTTPS destination.
pi-jev
y0usaf · Security & Guardrails
A Pi extension that flags tool risks before execution and checks output for secrets and failure types.
pi-jev-auto-mode
jomatsu · Security & Guardrails
Adds rule checks to Pi commands and file operations, then uses Jev to assess cases that need further judgment.
jev-judgment
HyunjunJeon · Security & Guardrails
Adds judgment checks for authorization, operation risk, and failure causes to coding Agents.