explaingit

jslint-org/jslint

Analysis updated 2026-07-03

3,663JavaScriptAudience · developerComplexity · 1/5Setup · easy

TLDR

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.

Mindmap

mindmap
  root((jslint))
    What it does
      Code quality checks
      Coverage reports
      Directory scanning
    How to use
      Command line
      Import as module
      Vim and VSCode plugins
      Web demo at jslint.com
    Configuration
      Inline directives
      Browser or server mode
      Rule adjustments
    Distribution
      Single file jslint.mjs
      No dependencies
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Scan a JavaScript file or entire project directory for code quality issues from the command line before committing.

USE CASE 2

Generate code coverage reports alongside quality checks without installing a separate coverage tool.

USE CASE 3

Paste JavaScript into jslint.com to instantly check code quality without installing anything locally.

USE CASE 4

Add JSLint to a CI pipeline to automatically reject commits that introduce code quality violations.

What is it built with?

JavaScriptNode.js

How does it compare?

jslint-org/jslintjschr/textillatesun0225sun/awesome-love-code
Stars3,6633,6623,664
LanguageJavaScriptJavaScriptJavaScript
Setup difficultyeasyeasyeasy
Complexity1/52/51/5
Audiencedeveloperdesignerdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Download the single jslint.mjs file, no installation or configuration required.

In plain English

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.

Copy-paste prompts

Prompt 1
Using jslint.mjs, write a Node.js script that scans all .js files in a project directory and outputs a summary of issues grouped by file.
Prompt 2
Show me how to add inline JSLint directives to a browser-targeted JavaScript file to tell JSLint it runs in a browser environment and relax the for-loop rule.
Prompt 3
How do I integrate JSLint into a GitHub Actions workflow to block pull requests that fail code quality checks?
Prompt 4
Using JSLint's coverage feature, show me how to generate a report for a Node.js test suite and identify which functions were never called.

Frequently asked questions

What is jslint?

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.

What language is jslint written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js.

How hard is jslint to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is jslint for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub jslint-org on gitmyhub

Verify against the repo before relying on details.