JevLint-LE
Lint the questions you send to TypeSafe's Jev model as you type, with no API key and no network calls. An optional command asks Jev itself to check a file
No editor in the loop? npx -y jevlint-le --mcp runs the same engine as an MCP server, so an agent can call lint_text with nothing else installed. Every way to install it.
What JevLint-LE does
Jev answers the question you wrote, which is not always the one you meant. JevLint-LE finds the questions a project sends to TypeSafe's Jev model, in JSON, JavaScript, TypeScript, Python, Rust and Go, and reports the ones written in a way documented to fail: a choice with no fallback option, a score given a map where it takes a list, a type that does not exist, a question that turns on a word with no stated line. Linting runs as you type with no API key and no network. A part of a question that is built at runtime is counted as not read, never guessed at. One command, run by you with your own key, asks Jev itself to check a file.
What people use it for
Catch it while typing
Findings appear in the editor as a question is written, with a quick fix where the fix is not a guess.
Check a pull request
The same checks run from the command line, with output for a terminal, as JSON, or as GitHub annotations.
Hand it to an agent
The MCP server offers lint_text, lint_paths and list_rules, so an agent can check the questions it writes.
7 commands in the palette
Open the command palette and type the name. Nothing is bound to a shortcut by default — the editor's keymap is the user's, not ours.
jevlint-le.lintFilejevlint-le.lintWorkspacejevlint-le.openSettingsjevlint-le.checkWithJevjevlint-le.setApiKeyjevlint-le.clearApiKeyjevlint-le.probeQuestionInstall JevLint-LE
VS Code
ext install nolindnaidoo.jevlint-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension nolindnaidoo.jevlint-leVS Code forks pull from Open VSX. The id is the same as on the Marketplace.
Zed
npx -y jevlint-le --mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and lint_text appears in its tool list. There is no one-click listing in Zed's extension registry yet.
AI agents
npx -y jevlint-le --mcpRuns JevLint-LE's engine as an MCP server, so an agent can call lint_text with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where it ships
One engine, 5 places to get it. Copy the one for the editor you use.
MCP server
the same engine, callable by an agent with no editor in the loopnpx -y jevlint-le --mcpMCP registry
the name it will be listed underio.github.nolindnaidoo/jevlint-leOpennot listed yet — this links the sourceZed
as a custom MCP server todaynpx -y jevlint-le --mcpOpenno listing yet — this links Zed’s instructions for adding it by hand
Where JevLint-LE lives
- VS Code Marketplacejevlint-le
- Open VSXfor Cursor and VSCodium
- npmjevlint-le
- GitHubsource, issues, changelog
The other 16
Extract every string in a codebase, with its position, so a person can read them
Extract every hardcoded number in a codebase, so a person can check them
Extract every file path in a codebase, and say whether it still points at anything
Extract every color in a codebase, and say which ones are not in your palette
Extract every URL in a codebase, with its protocol and exact position
Extract every date and timestamp, and the exact instant each one resolves to
Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name
Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside
Extract every IP address, CIDR block and MAC, normalized and classified by scope
Find every regex in a codebase, and report which can be driven into catastrophic backtracking
Check whether a page is scrapeable before the scraper is written, and say when it cannot tell
Find where one dependency is constrained differently across a repository's manifests
Identify the i18n library a project uses, then audit its catalogs by that library's rules
Find hardcoded credentials in a codebase, and never print one into the report
Compare the dotenv files in a tree, and say which keys are missing from which
Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts