Skip to content

Jev directory

Jevlint — codegirl-007

A Go linter that checks code against plain-language rules: Tree-sitter extracts code units, then each one is sent to Jev or another configured decision provider to decide whether it passes, with caching and eval fixtures.
Stars
125
Language
Go
License
MIT
Reading time
2 min
Published by
Community
Author
codegirl-007
Last verified
Oct 2026

codegirl-007/jevlint

User repository on GitHub

View on GitHub

A linter to codify code taste using Jev

Forks
5
Last pushed
Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.

Languages
Go
Platforms
CLI
Capabilities
Open sourceRequires API key

Highlights

  • Commands: jevlint init, doctor, check, eval, plugin, and version; init and doctor accept --json for machine-readable output.
  • The default provider is TypeSafe Jev, sending requests to api.typesafe.ai/v1/systemone with the jev-latest model by default.
  • Other providers via JEVLINT_PROVIDER: typesafe, jev, cloudflare (Clef models), clef, openrouter, and openai; Clef keeps the same request and response shape.
  • Building from source needs Go 1.26 or newer with CGO and a C compiler; prebuilt binaries cover linux and macos amd64/arm64 plus windows amd64.
  • --changed checks only git-modified files, --concurrency defaults to 4 Jev requests, and --clear-cache or --refresh-cache manage cached evaluations.

Quickstart

bash
go install github.com/codegirl-007/jevlint/cmd/jevlint@latest
cd your-project
jevlint init
export TYPESAFE_API_KEY=apikey_...
jevlint doctor
jevlint check .

Watch out

Copy reviewed against the repo README on 2026-10-15. The README documents commands, flags, providers, and configuration but publishes no accuracy, latency, or cost benchmarks for the decisions, and without rules in .jevlint.json the check command has nothing to evaluate. Credentials are read from environment variables only.

Questions about this entry

Short answers drawn from the linked project or page.

Other listings of this project

Forks and copies of this project in the directory. This entry is the canonical one.

16GitHub stars
A linter whose rules are plain-English yes/no questions about code — secrets in logs, retry loops that run forever, leaked error messages — answered by TypeSafe's Jev as calibrated probabilities, with output shaped like any other linter.
Jev Tools & CLIs#community#catalog-import#logicrw
12GitHub stars
Command-line checker that asks Jev whether each selected source file violates a plain-English convention, returning file-level probabilities for an agent or CI step to act on.
Jev Integrations & Adapters#community#jevbest#catalog-import
12GitHub stars
Semantic lint that checks code against plain-English conventions via Jev and reports file-level violation probabilities for agents and CI.
Jev Agents & MCP#community#jevbest#catalog-import

From the Jev guides

Original write-ups on what this entry is for.

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai