Skip to main content

jevotron

Find the fields worth a second look. A CLI for field-level anomaly detection in tabular, structured, and text files, SQLite, and DuckDB, powered by Jev.

Preview the input, scan every entry, and export a focused review queue. Each chunk is independent and sees the same optional guidance and exemplars. SQLite caching reuses assessments across file versions.

Install and run

Requires Python 3.12+ and uv. From this checkout:

uv tool install .
jevotron --help

# Preview is free and needs no API key.
jevotron preview examples/airports/spiked.csv \
  --id-column ident --field /iso_country --limit 1

# Get a key from https://console.typesafe.ai/ and set it in this shell.
export TYPESAFE_API_KEY="your-api-key"

jevotron scan examples/airports/spiked.csv --guidance "Check airport locations."

jt is a short alias for jevotron; both accept the same commands and options. Database files are detected by their headers, even with an unfamiliar extension. No export or database configuration is needed; DuckDB support is included in the installation:

jt tables inventory.db                          # List tables, columns, and keys
jt preview inventory.db                         # Preview rows, no API key
jt scan warehouse.duckdb --table products        # Select a table
jt scan inventory.db                            # Scan all user tables

Databases are opened read-only. Each row is an entry, each column is a field, and primary keys supply table-qualified IDs. See the database guide for examples and selection rules.

API key: Live scans require TYPESAFE_API_KEY from the TypeSafe dashboard. An existing environment variable is used automatically; preview and fully cached runs need no key. Full setup instructions.

For development, use uv sync and uv run jevotron .... The CLI uses Typer, with grouped help and shell completion:

jevotron scan --help
jevotron formats
jevotron formats csv
jevotron --install-completion

Agent skills

Give your agent a large data file and a review question. The jt-triage skill teaches it to preview a few records, run a focused pilot, inspect a small queue of candidates, refine the guidance, and expand the scan. Full results stay on disk; the agent reads the cases that need reasoning. Cached assessments make repeat runs cheaper when the requests are unchanged.

npx skills add cmungall/jevotron --skill jt-triage

The skill installer supports multiple agents; it installs instructions and a local shortlist helper. Install the CLI separately with uv tool install git+https://github.com/cmungall/jevotron.git and set TYPESAFE_API_KEY for live scans.

Try: “Use jt to find inconsistent country assignments in this large airport file. Pilot the rules, investigate the strongest cases, then scan the full file and give me a review queue with source locations.”

Skill catalog · Installation and workflow guide · Skill instructions

Documentation

Read the published documentation.

A Material for MkDocs site with light/dark modes, search, downloadable examples, and a CLI reference generated from the actual commands:

uv run --group docs mkdocs serve

Open http://127.0.0.1:8000. Build static files with uv run --group docs mkdocs build --strict. Changes on main are published to GitHub Pages by the documentation workflow.

Examples

Example Includes
Airports Public-domain CSV, baseline and spiked versions, provenance, known changes
Inventory Synthetic YAML with written rules and a selected exemplar
Units Synthetic OBO with repeated tags and a custom local config

Flags handle common tasks. For custom formats or reusable settings, pass --config jev_config.py; a parser is an ordinary Python function yielding chunks. The advanced docs cover that contract.

Development

just wraps the checks. just check is exactly what CI runs, so a green local run means a green pull request.

just install      # sync the dev and docs dependency groups
just check        # lint, tests, strict docs build, package build
just              # list every recipe

Individual steps are available too: just test, just doctest, just lint, just fix, just docs, just serve, just build. just mypy runs the type checker, which is not yet clean and so is not part of just check.

Unit tests use fake responses and remove the API key; they make no paid calls.

Release files for jevotron 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jevotron 0.1.0
File Size Uploaded
jevotron-0.1.0.tar.gz 24.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for jevotron 0.1.0
File Interpreter ABI Platform
jevotron-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 53.9 kB

Release files / jevotron-0.1.0.tar.gz

Download URL jevotron-0.1.0.tar.gz
Size 24.7 kB
Tags Source
SHA-256 checksum
How to use checksums
fe651a65778565fa29e12cbf0285146a3f17998a356b3008d4b5d53e34fef913
BLAKE2b-256 checksum
How to use checksums
4ec4f6fedb48c3cc04a5ca3784c11b2959ce95bbae8425fb4bc172b849a59f11
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / jevotron-0.1.0-py3-none-any.whl

Download URL jevotron-0.1.0-py3-none-any.whl
Size 29.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fe524f958248e6a752c05f13cf7ec9fb70b10bfe25c32882d28dc6c48ab2993b
BLAKE2b-256 checksum
How to use checksums
235a980c3569dae5cb50bbe014e89a73135303f645fc61a44dd1117c412353ff
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page