Analyzed
about 12 hours
ago.
based on code collected
2 days
ago.
Project Summary
JSLint takes a JavaScript source and scans it. If it finds a problem, it returns a message describing the problem and an approximate location within the source. The problem is not necessarily a syntax error, although it often is. JSLint looks at some style conventions as well as structural problems. It does not prove that your program is correct. It just provides another set of eyes to help spot problems.
In a Nutshell, JSLint...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a average size development team
with increasing Y-O-Y commits -
...
took an estimated 4 years of effort (COCOMO model)
starting with its first commit in November, 2010
ending with its most recent commit 19 days ago
Quick Reference
https://github.com/douglascrockf...
The JSON License
Permitted
Forbidden
Required
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Poor security track-record
Favorable security track-record
Vulnerability Exposure Index
Many reported vulnerabilities
Few reported vulnerabilities
Did You Know...
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
data presented on the Open Hub is available through our API
-
...
55% of companies leverage OSS for production infrastructure
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
30 Day SummaryAug 21 2026 — Sep 20 2026
|
12 Month SummarySep 20 2025 — Sep 20 2026
|
