Static analysis tool for JavaScript

2.10.2  •  Published 7 months ago  •  by jshint  •  Unknown License

[ Use it onlineDocsFAQInstallContributeBlogTwitter ]

NPM version Linux Build Status Windows Build status Dependency Status devDependency Status Coverage Status

JSHint is a community-driven tool that detects errors and potential problems in JavaScript code. Since JSHint is so flexible, you can easily adjust it in the environment you expect your code to execute. JSHint is open source and will always stay this way.

Our goal

The project aims to help JavaScript developers write complex programs without worrying about typos and language gotchas.

Any code base eventually becomes huge at some point, so simple mistakes — that would not show themselves when written — can become show stoppers and add extra hours of debugging. So, static code analysis tools come into play and help developers spot such problems. JSHint scans a program written in JavaScript and reports about commonly made mistakes and potential bugs. The potential problem could be a syntax error, a bug due to an implicit type conversion, a leaking variable, or something else entirely.

Only 15% of all programs linted on jshint.com pass the JSHint checks. In all other cases, JSHint finds some red flags that could’ve been bugs or potential problems.

Please note, that while static code analysis tools can spot many different kind of mistakes, it can’t detect if your program is correct, fast or has memory leaks. You should always combine tools like JSHint with unit and functional tests as well as with code reviews.

Reporting a bug

To report a bug simply create a new GitHub Issue and describe your problem or suggestion. We welcome all kinds of feedback regarding JSHint including but not limited to:

  • When JSHint doesn’t work as expected
  • When JSHint complains about valid JavaScript code that works in all browsers
  • When you simply want a new option or feature

Before reporting a bug, please look around to see if there are any open or closed tickets that discuss your issue, and remember the wisdom: pull request > bug report > tweet.

Who uses JSHint?

Engineers from these companies and projects use JSHint:

And many more!


Most files are published using the standard MIT Expat license. One file, however, is provided under a slightly modified version of that license. The so-called JSON license is a non-free license, and unfortunately, we can’t change it due to historical reasons. This license is included as an in-line within the file it concerns.

The JSHint Team

JSHint is currently maintained by Rick Waldron, Caitlin Potter, Mike Pennisi, and Luke Page. You can reach them via admin@jshint.org.

Previous Maintainers

Originating from the JSLint project in 2010, JSHint has been maintained by a number of dedicated individuals. In chronological order, they are: Douglas Crockford, Anton Kovalyov, and Mike Sherov. We appreciate their long-term commitment!

Thank you!

We really appreciate all kinds of feedback and contributions. Thanks for using and supporting JSHint!

We are hiring frontend and backend developers!
Come and help us build the ultimate open source directory 🔥


Weekly Downloads



Last ver 7 months ago
Created 9 years ago
Last commit 4 months ago
2 days between commits


Node version: 6.16.0
3304.7K unpacked

Legal and Compliance

License Unknown
Not OSI Approved
0 vulnerabilities


142 contributors
Mike Pennisi
Maintainer, 323 commits, 26 merges, 150 PRs
Works at bocoup
Rick Waldron
Maintainer, 166 commits, 180 merges, 15 PRs
Works at Bocoup
Anton Kovalyov
Maintainer, 75 commits, 164 merges, 9 PRs
Works at Medium
Luke Page
Maintainer, 59 commits, 43 PRs
Works at SaxoBank
Nicolò Ribaudo
52 commits, 62 PRs
Caitlin Potter
Maintainer, 45 commits, 1 merges, 42 PRs
Works at Igalia
© 2019 Devstore, Inc.
Devstore helps developers find and use open-source packages, so they can focus on building amazing things