User repository on GitHub
Configurable semantic linting powered by Jev, with file-level NOUL judgments and a magic-strings plugin.
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Integrations & Adapters
JevLint — iamtoomas
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.
- Stars
- 12
- Language
- TypeScript
- License
- MIT
- Published by
- Community
- Author
- iamtoomas
- Last verified
- Oct 2026
About this project
Write coding conventions in plain English. JevLint checks what your code means, semantically, so your coding agent can fix what syntax rules miss. Use it in a write → check → fix → repeat workflow: your agent writes code, JevLint checks it against your conventions, and the agent uses the findings to make the next edit. Run it from your terminal, an agent’s verification step, or CI. Your agent or workflow controls when to run checks and how to fix findings; JevLint supplies the judgments.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- TypeScript
Highlights
- Ships magic-strings and descriptive-names checks, plus custom yes-or-no plugins defined as instruction text in a folder.
- Default finding threshold is 0.8 with per-run overrides, pretty or JSON output, and stable exit codes for gating.
- Dry runs print request JSON without calling the API, while glob quoting and ignore flags control the file scope.
- Scanning skips secrets and credentials paths by name, though other files can still carry sensitive values.
Watch out
Findings are file-level signals without line diagnostics or fixes, and dry runs still execute plugin code with normal permissions. 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.
Syntax rules miss vague names and ad-hoc string constants, so JevLint judges what the code means against your convention text and hands probabilities back for your agent workflow to fix.
Export a plugin object with an id, yes-or-no instructions, and a message, then register its directory in config with file and ignore scopes; instructions can be a string or a structured object.
No. It skips the API call and key requirement but still imports and runs configured plugins with full Node permissions, so only run configurations and plugins you trust.
Use JSON output with an explicit threshold so only files at or above it fail with exit 1, while configuration or analysis failures exit 2 and clean runs exit 0.
Node 24 or newer, then npm install --save-dev @jevlint/cli and npx jevlint init from the project root. Init writes jevlint.config.json with magic-strings enabled, prettyPrint on and exclusions for tests and .d.ts files, and it never overwrites an existing config. Configuration is optional: without one it scans the current directory with magic-strings. Put JEV_API_KEY in a .env in the directory you run from; exported shell variables win over it.
Exit 0 is no findings and no analysis failures, though the summary can still list skipped files. Exit 1 is at least one file with a finding at or above the threshold. Exit 2 is a configuration or analysis failure, which is worth treating differently from a finding since it usually means the check did not run properly rather than that the code is bad.
magic-strings flags application-defined symbolic strings such as states, modes and actions that should be named constants, while exempting ordinary display text, paths and library-defined values. descriptive-names flags vague or misleading identifiers whose purpose is clear enough from the file to justify a better name, while allowing conventional short names, clear local names and externally defined API names. Both are file-level, so neither gives you a line to edit.
Other listings of this project
Forks and copies of this project in the directory. This entry is the canonical one.
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
Communityhuntedman/JevLintTypeScript
huntedman/JevLintTypeScriptMore Jev resources like this
69GitHub stars
Provider-neutral TypeScript runtime for System One decisions: write choice, noul, and score code once, then run it on TypeSafe Jev, local Reflex, any compatible /v1/systemone endpoint, or a custom provider.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
iamaamir/system-oneTypeScript
iamaamir/system-oneTypeScript15GitHub stars
Uncertainty-aware semantic control flow and routable procedures for Effect, with type-safe patterns and policies over Effect Decision and DecisionModel where uncertain answers stay explicit branches.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
doeixd/discernTypeScript
doeixd/discernTypeScript8GitHub stars
Shadcn registry search block that shows lexical hits instantly then re-ranks the top candidates with Jev intent scoring in one request, with keyword fallback on failure.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
kylemclaren/jevsearchTypeScript
kylemclaren/jevsearchTypeScript5GitHub stars
React library on npm where Jev judgments choose presentation: `Branch` picks a subtree, `Rank` orders or truncates a candidate set, `Gate` shows an affordance, and `useScore` returns a number you can use as an ordinary prop.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
etweisberg/jev-uiTypeScript
etweisberg/jev-uiTypeScript2GitHub stars
A Next.js workbench that converts OpenAI-compatible Chat Completions requests into Jev state and typed questions, compares chat output against structured judgments, and publishes saved question packs as proxy routes. The interface is mainly in Chinese.
Jev Integrations & Adapters#community#jevbest#catalog-import
Community
Chandler-Sun/chat2jevTypeScript
Chandler-Sun/chat2jevTypeScript0GitHub stars
n8n community node for TypeSafe's System One API, exposing yes or no, choice and score questions as workflow nodes, with an Evaluate Questions operation that batches several over one state in a single request.
Jev Integrations & Adapters#community#jevbest#catalog-import
From the Jev community
Posts from builders shipping with Jev right now.