jslint-org/jslint

JSLint, The JavaScript Code Quality and Coverage Tool

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Type:Library / SDKCategory(s):Code Quality & Static AnalysisDeveloper Tools
Added to GitGenius on September 19th, 2026
Created on November 12th, 2010
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 473
Total Stargazers: 3,654 (+0)
Total Subscribers: 152 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.3 hours
Mean response time: 43.3 hours
90th percentile: 3.2 days
Tracked items: 14

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,153 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

JSLint is a static code analysis tool for JavaScript that identifies quality issues and provides coverage reporting.

The tool analyzes JavaScript code to detect potential bugs, style violations, and other quality problems. It works by parsing source code and applying a set of linting rules that flag suspicious patterns and non-idiomatic constructs. The approach emphasizes strict checking to catch errors early in development.

JSLint suits developers and teams who want straightforward code quality enforcement without configuration overhead. It operates as a zero-config, zero-dependency tool, meaning it requires no setup files or external packages to run. The tool can be used in multiple environments: as a command-line utility for linting entire directories, as an imported module in both ES Module and CommonJS environments, or through a web-based demo interface. It generates detailed reports including coverage metrics alongside quality findings.

The project maintains three active branches with distinct purposes: a stable master branch for production use, a beta branch hosting a web demo, and an alpha branch for development work. All three branches run continuous integration checks and publish coverage reports and artifacts. The tool provides archived versions of previous web demos spanning multiple years, indicating a long development history with maintained backwards compatibility documentation.