This page's content is sourced from the JSHint project repository. If you spot an error, please open an issue or (better yet) make a pull request!

JSHint, A Static Code Analysis Tool for JavaScript

[ Use it onlineAboutDocsFAQInstallHackBlogTwitter ]

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

JSHint is a community-driven tool to detect errors and potential problems in JavaScript code. It is very flexible so you can easily adjust it to your particular coding guidelines and the environment you expect your code to execute in.

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 look around to see if there are any open or closed tickets that cover your issue. And remember the wisdom: pull request > bug report > tweet.

Issue Priority

  • P1: Something is throwing exceptions; broken JSHint backward compatibility.
  • P2: Something is not being parsed correctly.
  • P3: Features that the core team will work on once P2s and P1s are done.
  • P4: Patches welcome; The request is good, but low priority.


JSHint is distributed under the MIT License. One file and one file only (src/stable/jshint.js) is distributed under the slightly modified MIT License.

The JSHint Team

JSHint is maintained by Rick Waldron, Caitlin Potter, Mike Sherov, and Mike Pennisi.

Thank you!

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