jevbooks

← All projects

PII-Detector

acarbone/PII-Detector

PII detection in logs using TypeSafe Jev noul questions.

Compliance & Legal0.23Runner-up: Classification & RoutingQuestionnaireFlight recorder
Automated README summary

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

What it is

A proof-of-concept CLI that analyzes web-application log lines to decide whether they contain personally identifiable information (PII). It is aimed at developers and security engineers who need to detect free-text PII that regex-based scanners miss.

How it uses Jev

For each log line, the CLI sends a state { log_line } to Jev and asks a noul question contains_pii plus one noul per PII category. The returned probabilities are thresholded in code (default 0.5) to flag lines as PII. Category probabilities explain why a line was flagged.

Primitives:noul

Technique worth stealing

Ask multiple noul questions in one request to get both a main decision and per-category explanations with almost no extra latency.

Try it

npm install; cp .env.dist .env and set TYPESAFE_API_KEY; npm run detect

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.88
  • Shows a System One patternnot found in the excerpt0.12
  • Describes handling uncertaintynot found in the excerpt0.08
  • Reports measured numbersnot found in the excerpt0.17
  • Is a runnable toolnot found in the excerpt0.21
  • Top-10 learning shortlist signalnot found in the excerpt0.28
  • Is a replica of the modelnot found in the excerpt0.08
  • Solves a common problem (0–2)score on a 0–2 scale1.77 / 2
  • About JevFound in material0.98
Signals
Jev is core to the project0.88Shows a System One pattern0.12Describes handling uncertainty0.08Reports measured numbers0.17Is a runnable tool0.21Top-10 learning shortlist signal0.28Is a replica of the model0.0800.51Solves a common problem (0–2)1.77 / 2012

no-judgment band (0.40–0.60)

Design patterns
Questionnaire0.98Flight recorder0.80Viewfinder0.67Check-up0.53Prefetch0.34Traffic light0.24Question bank0.2300.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 26 Sept 2026.