Name With Owner	jshint/jshint
Primary Language	JavaScript
Program language	JavaScript (Language Count: 2)
Platform
License:	MIT License
Release Count	85
Last Release Name	2.13.6 (Posted on 2022-11-11 14:07:19)
First Release Name	2011-04-16 (Posted on 2011-04-16 10:05:33)
Created At	2011-01-19 22:28:53
Pushed At	2023-08-24 04:15:22
Last Commit At
Stargazers Count	8.9k
Watchers Count	292
Fork Count	1.7k
Commits Count	2.3k
Has Issues Enabled
Issues Count	2412
Issue Open Count	390
Pull Requests Count	527
Pull Requests Open Count	64
Pull Requests Close Count	622
Has Wiki Enabled
Is Archived
Is Fork
Is Locked
Is Mirror
Is Private

JSHint, A Static Code Analysis Tool for JavaScript

[ Use it online •
Docs • FAQ •
Install •
Contribute •
Blog • Twitter ]

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!

License

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!

JSHint

Github stars Tracking Chart

JSHint的目标

该项目旨在帮助JavaScript开发人员编写复杂的程序，而不用担心打字错误和语言错误。

只有15％的程序在jshint.com上通过JSHint检查。在所有其他情况下，JSHint会发现一些可能是错误或潜在问题的红旗。

请注意，虽然静态代码分析工具可以发现许多不同种类的错误，但它无法检测您的程序是否正确，快速或内存泄漏。您应该始终将JSHint等工具与单元和功能测试以及代码审查相结合。

Overview