Analyzed
2 days
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 small development team
with decreasing 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 2 months 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...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
you can embed statistics from Open Hub on your site
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
compare projects before you chose one to use
30 Day SummaryNov 30 2025 — Dec 30 2025
|
12 Month SummaryDec 30 2024 — Dec 30 2025
|
