Analysis updated 2026-07-03
Scan a JavaScript file or entire project directory for code quality issues from the command line before committing.
Generate code coverage reports alongside quality checks without installing a separate coverage tool.
Paste JavaScript into jslint.com to instantly check code quality without installing anything locally.
Add JSLint to a CI pipeline to automatically reject commits that introduce code quality violations.
| jslint-org/jslint | jschr/textillate | sun0225sun/awesome-love-code | |
|---|---|---|---|
| Stars | 3,663 | 3,662 | 3,664 |
| Language | JavaScript | JavaScript | JavaScript |
| Setup difficulty | easy | easy | easy |
| Complexity | 1/5 | 2/5 | 1/5 |
| Audience | developer | designer | developer |
Figures from each repo's GitHub metadata at analysis time.
Download the single jslint.mjs file, no installation or configuration required.
JSLint is a tool that reads JavaScript code and tells you what is wrong with it. Created by Douglas Crockford, one of the early architects of JavaScript, it has been around in various forms for over a decade and has a reputation for being strict. The idea is simple: you hand it a JavaScript file, it analyzes the code, and it reports any problems it finds. The tool is distributed as a single file called jslint.mjs with no external dependencies and no configuration required out of the box. You download that one file, point it at your JavaScript, and it works. You can run it from the command line, import it into another JavaScript program, or use it through editor plugins for Vim and VSCode. There is also a web demo at jslint.com where you can paste code and see results immediately without installing anything. Beyond catching code quality issues, JSLint can also generate coverage reports. Coverage tells you which parts of your code actually ran during a test, so you can see what was never tested. It connects to Node.js's built-in coverage data to produce these reports without requiring a separate coverage tool. For teams or individuals who want automatic quality checks, JSLint can be run across an entire directory of files in one command, making it practical for larger projects. It includes a range of optional directives you can add as comments inside your code to tell JSLint about your environment, such as whether the code runs in a browser or on a server, and to relax or tighten specific rules. The project is maintained actively, with a version number that matches the release date, and it runs automated checks across three branches to verify each change before it ships.
A strict, zero-dependency JavaScript code quality checker created by Douglas Crockford that analyzes JS files for problems from the command line, editor plugins, or a live web demo.
Mainly JavaScript. The stack also includes JavaScript, Node.js.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.