User repository on GitHub
Rust linter powered by configurable Jev rules, with a VS Code extension.
- Forks
- 1
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Agents & MCP
ErisLint
Rust CLI that sends selected source to the Jev API under JSON-defined choice rules and maps answers to warnings or errors.
- Stars
- 21
- Language
- Rust
- License
- AGPL-3.0
- Published by
- Community
- Author
- Eriskii
- Last verified
- Oct 2026
About this project
ErisLint is a Rust linter for code-quality rules you define in JSON. Ask whether a function is needlessly complicated, a name is misleading, or a comment adds anything useful, then map Jev's answers to warnings or errors. ErisLint sends the selected source code and context to TypeSafe's Jev API. Findings are model judgments; the diagnostic messages and thresholds come from your rules. It works as a CLI, with an optional VS Code extension.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- Rust
Highlights
- Starter erislint.json beside Cargo.toml with include globs, rule files, overrides, and explicit edition handling.
- Offline check-config and dry-run show parsing and exact questions without reading secrets or network calls.
- Compact, JSON, and all-answers outputs with 64-way concurrency, deny-warnings, and 0, 1, 2 exit codes for CI.
Watch out
Live checks need jev_key in the environment and API access; exhausted retries exit 2 with no partial report rather than passing silently. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
Rules ask whether code is needlessly complex or names mislead, and Jev returns probabilities your diagnostics map with confidence thresholds. Messages and levels come from your config, not the model.
No. Check-config validates offline and dry-run parses Rust and prints states and questions without reading the secret. The variable must be exactly jev_key and env files are never auto-loaded.
Connection issues and 408, 429, 500, 502, 503, and 504 responses retry up to three times with 1, 2, then 4 second waits plus jitter and Retry-After handling. Auth errors or invalid answers fail at once within concurrency limits.
Discovery stops at the repository root, include defaults to Rust files while target and git data are always skipped, and ignore files are respected. Overrides flip severity per path and off prevents evaluation without changing thresholds.
Rust 1.95 or newer and a TypeSafe key for live checks. Clone, then cargo install --path . --locked, and put Cargo's bin directory on PATH. The starter erislint.json sits beside your root Cargo.toml with version, model, include globs and rules; each rule has an id, a where clause, a typed question with instructions and criteria, and diagnostics that map an answer plus a min_confidence to a level and a message. A rule can also live in its own file listed under rule_files.
0 means the run completed without errors and warnings were allowed; 1 means errors were emitted, or warnings under --deny-warnings; 2 means configuration, syntax, filesystem, authentication or API failure. In CI, supply jev_key through the secret store and run erislint --check-config then erislint --deny-warnings --format compact. --errors-only only changes what is displayed, so deny-warnings still fails a run whose warnings are hidden.
The default is Rust-style diagnostics with a rule id, source location, the evaluated excerpt and a caret under the declaration, ending in Found 1 warning or No issues found. --format compact prints one diagnostic per line, --format json adds an answers array for every evaluated rule whether or not it fired, each carrying the full option probabilities, selected choice, confidence, rubric and model, and --all-answers prints those probabilities in text. Color is automatic and honours NO_COLOR.
More Jev resources like this
35GitHub stars
Rust terminal tool that asks Jev noul, choice and score questions about piped text or files and returns calibrated probabilities with stable exit codes for shell scripts, CI jobs and agents.
Jev Agents & MCP#community#jevbest#catalog-import
Community
shaharia-lab/jev-cliRust
shaharia-lab/jev-cliRust12GitHub stars
Single-binary linter whose YAML rules are plain-language questions sent to the Jev model as yes-no judgments with probabilities, fitting CI jobs and pre-commit hooks.
Jev Agents & MCP#community#jevbest#catalog-import
Community
virolea/lintusRust
virolea/lintusRust22GitHub stars
Sentence-driven runner where one command is matched to installed reflex programs, planned up front with per-step probabilities and gates.
Jev Agents & MCP#community#jevbest#catalog-import
Community
evoke-build/evokeRust
evoke-build/evokeRust2GitHub stars
Rust client that lets Jev choose the model and privacy tier for NEAR AI Cloud calls. A client-controlled monthly cap in cents is combined with Jev scores for complexity and sensitivity and nouls for private TEE, risk and urgency, then the NEAR catalog is filtered to what survives that choice.
Jev Agents & MCP#community#jevbest#catalog-import
Community
iJ03l/jearRust
iJ03l/jearRust6GitHub stars
A Rust CLI that finds files and line ranges with two ingredients: a stateless in-memory BM25 pass for recall and Jev calibrated judgments for precision. No embeddings, no vector database, no index directory, no repository state.
Jev Agents & MCP#community#jevbest#catalog-import
Community
romeromarcelo/jev-retrievalRust
romeromarcelo/jev-retrievalRust330GitHub stars
A local-first macOS coding workspace that runs Claude Code, Codex, Cursor, Grok, Hermes, and pi over ACP, with a local Laya or hosted Jev selector choosing routes that the host then validates.
Jev Agents & MCP#community#jevbest
Community
codejunkie99/keelRust
codejunkie99/keelRustFrom the Jev community
Posts from builders shipping with Jev right now.