jev-git

What can you inspect while the original repository is unavailable?

The pinned upstream README and main.rs returned 404 when checked on 2026-10-24. The preceding description is historical and does not establish current maintenance or runtime behavior. The lab below is this site’s own advisory Git implementation, not a reproduction of the Rust binary, its two Noul questions, or its performance claims.

Compare the responsibility boundaries

The historical project uses Noul for secret-like and destructive changes. Our example first blocks sensitive paths and common credential patterns locally, then asks three different questions about change type, risk and human review. The local layer decides whether sending is allowed; the model layer only supplies semantic suggestions. Pattern matching cannot establish the absence of secrets, so inspect inputs before a real upload.

Four cases check application behavior

Synthetic responses exercise a valid suggestion, missing credentials, a sensitive file and an incomplete response. None grants merge permission: blocking mode returns 1 for all four. A report-mode exit of 0 means the reporting step completed, not that the change is safe.

// This site's advisory Git lab, not the upstream Rust jev-git binary.
// Node 20+. Synthetic responses only; no key, network request or Git write.
import assert from 'node:assert/strict';
import { reviewDiff, exitCode } from './jev-pr-review.mjs';

const answers = {
  change_type: { type: 'choice', choice: 'fix', confidence: 0.8 },
  risk: { type: 'score', score: 1 },
  needs_human_review: { type: 'noul', noul: 0.6 },
};
const input = { names: 'M\0src/app.js\0', patch: '+return true;', apiKey: 'offline-only' };
const response = async () => ({ ok: true, json: async () => ({ answers }) });
const noUpload = async () => { throw new Error('Must not send this input'); };
const cases = [
  ['valid suggestion', await reviewDiff({ ...input, fetchImpl: response }), 'report_only'],
  ['missing key', await reviewDiff({ ...input, apiKey: '', fetchImpl: noUpload }), 'missing_credentials'],
  ['sensitive file', await reviewDiff({ ...input, names: 'M\0.env\0', fetchImpl: noUpload }), 'sensitive_input'],
  ['incomplete response', await reviewDiff({ ...input, fetchImpl: async () => ({ ok: true, json: async () => ({ answers: {} }) }) }), 'invalid_response'],
];
for (const [name, result, expected] of cases) {
  assert.equal(result.status, expected);
  assert.equal(exitCode(result, 'blocking'), 1);
  console.log(`${name}: ${result.status}; blocking exit=1`);
}
console.log('OFFLINE FIXTURES: four application checks passed; no upstream binary or model-quality test.');

Download the advisory implementation · Download the four-case lab

node jev-git-offline.mjs

Place both files in one directory and run with Node 20+. Expect four status lines and a final line beginning OFFLINE FIXTURES. The lab does not read a repository, write Git, contact a provider or establish model accuracy.