jevbooks

← All projects

jev-tos-checker

shohei81/jev-tos-checker · Homepage

Chrome extension flagging abusive ToS clauses with Jev.

Compliance & Legal0.99Runner-up: Content ModerationViewfinder
Automated README summary

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

What it is

A Chrome extension that reads the terms of service on the current page, splits it into clauses, and flags clauses that may work against the user. It is for anyone who wants to spot unusual clauses in long terms, in any language.

How it uses Jev

Each clause, judged together with surrounding paragraphs, is sent to Jev as a typed question per category (eight kinds of abusive terms). Jev returns a probability that the clause is abusive; a clause is marked Caution when that probability is 70% or higher, and results are grouped by category with links to the original text.

Primitives:score

Technique worth stealing

Judge each clause with its surrounding paragraphs so exceptions in nearby text are taken into account, and only flag clauses far beyond common practice.

Try it

Download the zip from Releases, load the folder unpacked in chrome://extensions, then set an API key or analysis server URL.

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.14.0
Project signals
jev-1.14.0
Category
jev-1.14.0
Pattern tags
jev-1.14.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.82
  • Shows a System One patternnot found in the excerpt0.09
  • Describes handling uncertaintynot found in the excerpt0.04
  • Reports measured numbersnot found in the excerpt0.02
  • Is a runnable toolFound in material0.98
  • Top-10 learning shortlist signalnot found in the excerpt0.17
  • Is a replica of the modelnot found in the excerpt0.04
  • Solves a common problem (0–2)score on a 0–2 scale1.16 / 2
  • About JevFound in material0.97
Signals
Jev is core to the project0.82Shows a System One pattern0.09Describes handling uncertainty0.04Reports measured numbers0.02Is a runnable tool0.98Top-10 learning shortlist signal0.17Is a replica of the model0.0400.51Solves a common problem (0–2)1.16 / 2012

no-judgment band (0.40–0.60)

Design patterns
Viewfinder0.74Question bank0.2800.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 Oct 2026.