Developer Tools
jev-lint
Source: zdenham/jev-lint
Last updated 2026-09-20 · benchmark checked 2026-11-18 · unchanged since 2026-11-02 — deterministic & reproducible
jev-lint is a GitHub-hosted project available at github.com/zdenham/jev-lint.
jev-lint at a glance
jev-lint is a command-line tool that checks JavaScript and TypeScript code against project conventions written in plain English, intended for JavaScript developers, TypeScript developers, and project maintainers.
Good for
- Enforcing project coding conventions that are written in plain English rather than code-based lint rules
- Running checks on changed files before they merge, using compact, pretty, or JSON output
- Reviewing findings first before turning them into CI-blocking errors, since the tool is an early release
Questions people ask
What does jev-lint actually do?
It checks JavaScript and TypeScript files against rules written in plain English and reports possible violations; it does not edit the code.
How do I install and set it up?
You clone the GitHub repository and run npm ci, npm run build, and npm link, which requires Node.js 22.22+ and Git.
Do I need an API key to use it?
Yes, live checks require a Vercel AI Gateway API key, since selected source code and rules are sent to Jev through Vercel AI Gateway using your credits.
Can jev-lint fix my code automatically?
No, the tool only reports findings and does not edit code.
Is there a limit on how much a check can cost?
Yes, defaults are $1, 10 files, 10 requests, and 100,000 total input bytes, and these can be changed in the config file or overridden per run with command-line flags.
Written by Legit.Show from github.com on 2026-09-30. It does not change the score.
Are you the maker of jev-lint? Claim this listing. It is free, takes a meta tag, a DNS record or GitHub admin rights, and never changes the score.
Launched something? Add your product, free.
To cite this score: legit.show/s/gh-jev-lint/2026-11-18. That address never changes; this page moves with every re-measure.
Legit.Show scored jev-lint 38/100 on 2026-11-18, measured across 3 of 7 frames from its public surface. legit.show/s/gh-jev-lint/2026-11-18
Is jev-lint production-ready?
Legit.Show scores jev-lint 38 out of 100 — the simple average of its 3 measured frames. Legit.Show ran its deterministic 7-Frame production-readiness benchmark on jev-lint (github assessment), measured from the public surface with no LLM in the scoring path. Its strongest frame is Security; its weakest is Discoverability. 3 of the seven frames returned a score; Performance, Accessibility, Privacy and Reliability were not measurable on this service and are recorded as null — not as zero. Maintenance is an additional frame from the open-source teardown, scored separately from the seven. Every frame it averages is published with its evidence on the Legit.Show listing.
The 7 Frames
- Performance — not measurable on this service (null — not scored as 0)
- Accessibility — not measurable on this service (null — not scored as 0)
- Security — 40/100How this compares across the catalogue: The Web Security Baseline
- Privacy — not measurable on this service (null — not scored as 0)
- Reliability — not measurable on this service (null — not scored as 0)
- Standards — 40/100
- Discoverability — 35/100
Open-source teardown
Scored separately — not one of the seven.
- Maintenance — 80/100
What we measured
- No Content-Security-Policy and no HSTS.
- No privacy policy found.
- Sets cookies / loads scripts with no consent prompt.
Who built it
Zac Denham (@zac_denham)
Who it's for
JavaScript developers · TypeScript developers · Project maintainers
Sources and updates
- Description
- Taken from github.com's own website on 2026-09-20.
- Code
- github.com/zdenham/jev-lint.
- Benchmark
- Measured by Legit.Show from the live site, the way any visitor sees it — with no access to its code or accounts. Same method for every product, and no AI decides the score. Last checked 2026-11-18.
Put together from public information, without jev-lint's involvement. If anything here is wrong, tell us and a person will check it.
Visit jev-lint → · Alternatives to jev-lint → · How this was measured →