Hadolint
6.4#8 in lintersFree planFree planWebLinuxmacOSWindows
VisitHadolint vs JSHint
What both publish
| Fact | Hadolint | JSHint |
|---|---|---|
| Configuration | Users can configure ignored rules, severity overrides, failure thresholds, output format, label schemas, and trusted registries. | Projects can configure JSHint with a .jshintrc file, package.json jshintConfig or the CLI --config option. |
| Editor integrations | Documented editor integrations include VS Code, Atom, Emacs, Geany, Sublime Text, Vim, and NeoVim. | The project lists integrations for Vim, Emacs, Sublime Text, Atom, TextMate, Visual Studio, VS Code, Brackets, Eclipse, NetBeans, JetBrains, Notepad++ and Gedit. |
| Latest release | The release page opened for this research lists v2.15.1 as the latest release. | GitHub lists JSHint 2.13.6 as the latest release, dated 2022-11-11, with fixes for const initialization and an error message. |
| License | The repository identifies its license as GPL-3.0. | JSHint is licensed under the MIT Expat license. |
| Purpose | Hadolint is a Dockerfile linter that checks Dockerfiles for errors and best practices. | JSHint is a community-driven static analysis tool that detects errors and potential problems in JavaScript code. |
Hadolint plans
- HadolintFree
JSHint plans
- JSHintFree
Pick Hadolint if…
Hadolint suits developers who want to check Dockerfiles and Bash commands in RUN instructions. Its documented CI, editor and pre-commit integrations may fit teams incorporating linting into their development workflows.
Pick JSHint if…
JSHint suits JavaScript developers who want automated checks for syntax issues and common language pitfalls. It can fit into workflows using Node.js, supported editors, or listed build integrations.