jevlint
A model-based linter that tells you what to refactor first.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/INDXDev/jevlint with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/INDXDev/jevlint'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/indxdev--jevlint)HTML
<a href="/listings/indxdev--jevlint"><img src="/api/listings/indxdev--jevlint/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
npm install -g @indxjp/jevlint # or: pnpm add -g @indxjp/jevlint jevlint --version
Requires Node.js 24.22.1 or later (or 22.23.4, or 26.12.1, on those lines).
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 14 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- {
- "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
- "name": "jevlint",
- "description": "A model-based linter that tells you what to refactor first.",
- "owner": { "name": "INDX", "url": "https://github.com/INDXDev" },
- "plugins": [
- {
- "name": "jevlint",
- "description": "Rank what to refactor first with jevlint, and review what a change made worse.",
- "source": "./",
- "category": "development"
- }
- ]
- }
README.md · README · 346 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <p align="center">
- <a href="README.ja.md">日本語</a> · <a href="README.zh-CN.md">简体中文</a> · <b>English</b>
- </p>
- <p align="center">
- <a href="#try-it-now"><img src="docs/assets/hero.svg" alt="jevlint: know what to refactor first" width="820"></a>
- </p>
- <p align="center">
- <a href="https://www.npmjs.com/package/@indxjp/jevlint"><img src="https://img.shields.io/npm/v/@indxjp/jevlint?color=cb3837&logo=npm" alt="npm version"></a>
- <a href="https://github.com/INDXDev/jevlint/actions/workflows/ci.yml"><img src="https://github.com/INDXDev/jevlint/actions/workflows/ci.yml/badge.svg?branch=main" alt="CI status"></a>
- <img src="https://img.shields.io/badge/node-%E2%89%A524.22.1-339933?logo=nodedotjs&logoColor=white" alt="Node.js 24.22.1 or later">
- <img src="https://img.shields.io/badge/languages-TS%20%7C%20JS%20%7C%20Python%20%7C%20Go%20%7C%20Rust%20%7C%20more-89b4fa" alt="Languages: TypeScript, JavaScript, Python, Go, Rust and more">
- <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-a6e3a1" alt="MIT license"></a>
- </p>
- <p align="center">
- <a href="docs/getting-started.md"><b>Get started</b></a> ·
- <a href="docs/cli.md"><b>CLI</b></a> ·
- <a href="docs/presets.md"><b>Presets</b></a> ·
- <a href="docs/agents.md"><b>Coding agents</b></a> ·
- <a href="docs/README.md"><b>Docs</b></a>
- </p>
- # jevlint
- **A model-based linter that tells you what to refactor first.**
- ESLint tells you a line broke a rule. jevlint reads every file in your repository, scores how
- clean it is against principles you choose, and hands you a ranked list: messiest and most-changed
- files first. Then it writes the prompt that gets Claude Code or Codex to fix them.
- <p align="center">
- <img src="docs/assets/before-after.svg" alt="A diff of a fictional file, src/orders/total.ts. A deeply nested function named proc, with one-letter names, an any type and a magic number 0.9, becomes orderTotal, which uses filter, reduce and a named MEMBER_DISCOUNT constant. Its score rises from 18 to 92, nesting from 4 to 1 and complexity from 5 to 2." width="820">
- </p>
- <p align="center"><sub>Illustrative example on a fictional file.</sub></p>
- ## Try it now
- No install, no API key, and your code stays on your machine:
- ```sh
- npx @indxjp/jevlint --ast-only
- ```
- ## Install
- ```sh
- npm install -g @indxjp/jevlint # or: pnpm add -g @indxjp/jevlint
- jevlint --version
- ```
- Requires Node.js 24.22.1 or later (or 22.23.4, or 26.12.1, on those lines).
- ## See it work
- A team inherits `shop-api` and has one afternoon for cleanup. jevlint picks the file, explains why,
- hands it to Claude Code, and confirms the score went up.
- <p align="center">
- <img src="docs/assets/demo.gif" alt="Terminal recording: jevlint audit ranks src/orders/process.ts worst at 21 out of 100, jevlint explain lists its findings, jevlint fix runs Claude Code on it and the score rises to 84, and a second audit shows the repository score rise from 58 to 63." width="820">
- </p>
- <p align="center"><sub>Simulated run on a fictional project. <a href="docs/assets/demo/demo.tape">Recording script</a>.</sub></p>
- ## Why it is different
- - **Two kinds of judgement.** AST analysis measures what is measurable, such as complexity and
- nesting. A [decision model](docs/concepts.md#decision-models) answers what needs judgement, such
- as "do these names carry meaning?"
- - **Decision models, not chatbots.** Models like [TypeSafe AI's Jev](https://typesafe.ai) return
- calibrated scores and probabilities rather than prose. That makes them fast and cheap, and it means results can be ranked and cached.
- - **A ranking, not a wall of warnings.** Files are ordered by mess, git churn and size, so the
- first item is the one worth your time.
- - **Reviews of a change, not only a repository.** `jevlint pr` and `jevlint commits` show a file's
- score before and after, and only what the change made worse. `--intent` also holds a change
- against its message and your `AGENTS.md`, and `pr --acceptance` against the acceptance criteria
- of the issues it closes.
- - **Your own rules, in one sentence.** An ast-grep pattern picks the code and a yes/no question
- judges each match, so a model's verdict gets a line number.
- - **Most source languages.** TypeScript, JavaScript, Python, Go and Rust get exact metrics. Other
- languages get [approximate ones](docs/scoring.md#languages-without-a-grammar), with no extra install.
- - **Principles as presets.** Audit against ideas from well-known software books, or write your own
- in a few lines of TOML.
- - **Scores you can settle.** A `jevlint-score` comment fixes an accepted score with a reason, so
- nobody chases points. See [Pinning scores](docs/scoring.md#pinning-scores).
- - **Ready for coding agents.** `jevlint prompt | claude -p`, or let `jevlint fix` run the agent.
- A [Claude Code plugin](#fix-it-with-a-coding-agent) and an edit hook are included.
- - **Pay for an answer once.** Results are cached by content, and an
- [S3-compatible bucket](docs/caching.md#share-the-cache-through-object-storage) shares them across CI
- and your team.
- ## What it is not
- - **Not a replacement for your linter.** Keep ESLint, Ruff, Clippy and your type checker for what
- they can decide exactly. jevlint ranks what they cannot judge.
- - **Not a verdict.** Model scores are calibrated opinions. They vary between models and can move
- between model versions, so treat them as candidates for a person to review, pin a model version
- in CI, and use [`jevlint test`](docs/presets.md#testing-a-question) to see when a question drifts.
- - **Not private by default, once a provider is on.** Everything except `--ast-only` sends code to
- the provider you configure. See [Before you run it](#before-you-run-it).
- ## Quick start
- ```sh
- jevlint auth set typesafe # store a key once, per user
- jevlint init # create jevlint.toml in this repository
- jevlint audit --dry-run # see what would be sent, with no provider requests
- jevlint audit # rank the whole codebase
- ```
- No TypeSafe access? [Use another provider](docs/providers.md), such as `openai`, `cloudflare` or
- `gateway`.
- ## Fix it with a coding agent
- ```sh
- jevlint prompt --top 3 --copy # paste into any agent
- jevlint prompt | claude -p # or pipe it
- jevlint fix --agent claude # or run the agent, then re-score
- jevlint quickfix --agent claude # or let it only edit, then see the diff, new score and commit
- ```
- In Claude Code, install the plugin for a skill and `/jevlint:audit`, `/jevlint:explain` and
- `/jevlint:review`. Its edit hook is off until you turn it on:
- ```text
- /plugin marketplace add INDXDev/jevlint
- /plugin install jevlint@jevlint
- ```
- See [Coding agents](docs/agents.md).
- ## Keep documents and code in agreement
- `jevlint spec` turns your documents into a checklist, then checks code and documents against it:
- ```sh
- jevlint spec compile --copy # a prompt for your agent: write .jevlint/spec from the docs
- jevlint spec check # which files violate an item, and which items nothing implements
- jevlint spec drift # where the docs and the checklist disagree
- ```
- The checklist is YAML with two levels: a project checklist, and one per feature. Each file is first
- routed to its feature, then judged against that feature's items only. See
- [Spec-driven development](docs/spec-driven-development.md).
- ## Write your own rule
- An ast-grep pattern decides which code is looked at. One question decides whether it is a problem,
- and yes means a violation. Each hit is reported on its line:
- ```toml
- # jevlint.toml
- [[rules]]
- id = "catch-hides-failure"
- language = "typescript"
- pattern = "try { $$$ } catch ($E) { $$$ }"
- question = "Does this catch block swallow a failure the caller needed to know about?"
- message = "This catch hides a failure"
- fix = "Rethrow it, or return an error the caller must handle."
- threshold = 0.8 # optional: report at or above this probability
- ```
- Each match is one provider request, up to `max_rule_matches` per rule and file, and `--ast-only` skips
- rules. See [Semantic rules](docs/presets.md#semantic-rules).
- Prove a preset question works with `good-*` and `bad-*` fixtures, and catch a model update that
- moves it:
- ```sh
- jevlint test # every fixture must land on the right side
- jevlint test --record # save today's answers
- jevlint test --drift # ask again, and list what moved
- ```
- ## Review a change
- ```sh
- jevlint pr --ast-only # what this branch's pull request made worse
- jevlint pr 42 --ast-only # the same, by number
- jevlint commits --count 5 --ast-only # the same, commit by commit
- jevlint commits --count 5 --intent # also check each message and AGENTS.md against the diff
- jevlint pr 42 --acceptance # does it meet the criteria of the issues it closes?
- ```
- Your working tree stays as it is, and your own config applies, not the change's. `--intent` reads
- the repository's instructions from the base commit, so a change cannot rewrite what it is judged by.
- See the [CLI reference](docs/cli.md#jevlint-pr-number), and
- [Continuous integration](docs/ci.md#review-what-a-pull-request-changes) to run it on every pull request.
- Catch a regression before it is committed, with no key and no network:
- ```sh
- jevlint init --pre-commit # stops a commit that makes a file worse than HEAD
- ```
- ## Fail CI on a low score
- ```toml
- # jevlint.toml
- [scoring]
- fail_under = 60 # exit 1 below this
- ```
- On a legacy codebase, gate on what is new instead of on the score:
- ```sh
- jevlint baseline --ast-only # commit .jevlint/baseline.json
- jevlint audit --new --ast-only --format github # exit 1 on anything new, as PR annotations
- jevlint audit --ast-only --format sarif > jevlint.sarif # for code scanning
- ```
- See [CI](docs/ci.md).
- ## Related projects
- Jev made a linter an obvious thing to build, and several people built one independently. None of
- these is affiliated with this project. They answer different questions, so pick by what you need:
- | Project | Unit of judgement | Use it when you want |
- | --- | --- | --- |
- | **@indxjp/jevlint** (this one) | Whole files, ranked. Optional per-match rules | To know what to refactor first, across a repository, against named principles |
- | [jev-lint](https://github.com/mizchi/jev-lint) | One ast-grep match, one sentence | A large catalogue of shipped rules with fitted cutoffs, for code that contradicts its own comments and names |
- | [@hazymoon/jevlint](https://github.com/Ice-Hazymoon/jevlint) | A rule per question, in a TypeScript config | Hand-written review rules with exemptions, and mutation tests that measure recall |
- | [@phox-js/jevlint](https://github.com/Fox-Islam/jevlint) | A Jev query | To lint the queries you send to Jev, not your code. Also for PHP and Python |
- | [@diffpal/jevlint](https://www.npmjs.com/package/@diffpal/jevlint), now [LintPal](https://github.com/diffpal/lintpal) | Changed lines in a Git comparison | Your team's Markdown rules as pull request checks |
- Baselines, SARIF output, fixtures, drift checks and message checks here follow the lead of the
- first two projects above. jevlint, jev-lint and @hazymoon/jevlint all use
- [ast-grep](https://ast-grep.github.io) to read code.
- ## Reference
- <details>
- <summary><b>Commands</b></summary>
- | Command | What it does |
- | --- | --- |
- | `jevlint audit [paths...]` | Score files and rank them. Also the default command. |
- | `jevlint explain <file>` | Show every finding and score for one file. |
- | `jevlint architecture [paths...]` | Review the codebase, directories and classes, and rank them worst to best. |
- | `jevlint architecture compile\|show\|check\|drift\|plan` | Compile an architecture SSOT from the code with a coding agent, draw it, check code against it with no model, and keep it current. |
- | `jevlint pr [number]` | Review what a GitHub pull request changes: scores before and after, and what got worse. |
- | `jevlint commits [revision]` | Review commits the same way, one by one, from `HEAD` backwards. |
- | `jevlint baseline [paths...]` | Record today's issues, so `audit --new` reports only what is new. |
- | `jevlint test [questions...]` | Run preset fixtures, record their answers, and detect drift. |
- | `jevlint hook` | Report what an edit or a staged change made worse, for agents and pre-commit. |
- | `jevlint spec compile\|check\|drift\|list` | Spec-driven development: compile documents into a checklist, then check code and documents against it. |
- | `jevlint prompt [files...]` | Print or copy a fix prompt for a coding agent. |
- | `jevlint fix [files...] --agent <name>` | Run an agent on the worst files, then re-score them. |
- | `jevlint quickfix [files...] --agent <name>` | Have an agent only edit the worst files, one at a time, then show the diff side by side, re-score and commit each. |
- | `jevlint init` | Create a repository or user config. |
- | `jevlint auth set\|list\|remove\|env` | Manage API keys. |
- | `jevlint preset [list\|show\|default\|new\|edit\|add\|remove]` | Choose, view, write and manage principle presets. Alone, it opens a menu. |
- | `jevlint cache info\|clear` | Inspect or empty the result cache. |
- | `jevlint config show\|path` | Show the merged config and where it came from. |
- </details>
- <details>
- <summary><b>Configuration</b></summary>
- ```toml
- # jevlint.toml
- presets = ["readable-code", "solid"]
- include = ["src/**"]
- exclude = ["**/*.generated.ts"]
- [provider]
- name = "typesafe"
- model = "jev-latest"
- [scoring]
- scale = 100 # use 1 for scores from 0 to 1
- fail_under = 60 # exit 1 below this, for CI
- [weights]
- "readable-code.naming" = 3 # care about this more
- "solid.dependency-inversion" = 0 # turn this off
- ```
- </details>
- <details>
- <summary><b>Built-in presets</b></summary>
- | Preset | Focus |
- | --- | --- |
- | `full` | The default: every preset below, 97 questions in one request per file |
- | `readable-code` | Names, comments, control flow, time to understand |
- | `clean-code` | Small functions, one level of abstraction, honest error handling |
- | `solid` | The five object-oriented design principles |
- | `software-design` | Deep modules, information hiding, complexity management |
- | `code-smells` | Classic refactoring smells |
- | `clean-architecture` | Dependency direction, boundaries, framework independence |
- | `kiss-dry-yagni` | Simplicity, duplication, speculative code |
- | `security` | Input validation, injection, secrets, access checks, safe failure |
- | `documentation` | File purpose, doc comments on public code, stated contracts, accurate docs |
- | `bug-hunt` | 43 known defect classes, from CWE and other taxonomies, to rank where bugs hide |
- Presets paraphrase publicly discussed principles in our own words. They are not affiliated with or
- endorsed by the original authors or publishers. See [docs/presets.md](docs/presets.md).
- </details>
- ## Documentation
- Start with the [documentation index](docs/README.md).
- - [Getting started](docs/getting-started.md)
- - [Concepts](docs/concepts.md)
- - [CLI reference](docs/cli.md)
- - [Configuration](docs/configuration.md)
- - [Providers](docs/providers.md)
- - [Presets](docs/presets.md)
- - [Scoring](docs/scoring.md)
- - [Architecture review](docs/architecture-review.md)
- - [Architecture-driven development](docs/architecture-driven-development.md) and the [SSOT reference](docs/architecture-reference.md)
- - [Spec-driven development](docs/spec-driven-development.md) and the [spec reference](docs/spec-reference.md)
- - [Coding agents](docs/agents.md)
- - [Caching](docs/caching.md)
- - [Continuous integration](docs/ci.md)
- - [JSON output](docs/json-output.md)
- - [Security and privacy](docs/security.md)
- - [Troubleshooting](docs/troubleshooting.md)
- - [Architecture](docs/architecture.md) and [code reference](docs/code-reference.md)
- ## Before you run it
- An audit sends the contents of your source files to the provider you configure. Read
- [Security and privacy](docs/security.md) first if your code is confidential. `audit --ast-only`
- never touches the network.
- ## Contributing
- See [CONTRIBUTING.md](CONTRIBUTING.md). To report a vulnerability, see [SECURITY.md](SECURITY.md).
- ## License
- [MIT](LICENSE)
- jevlint is an independent open-source project. It is not affiliated with or endorsed by TypeSafe
- AI, Cloudflare, Microsoft, OpenAI, Vercel or Anthropic. All product names are the property of their
- respective owners.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.