gruntjs/grunt-contrib-jshint

Validate files with JSHint.

Hosted by OpenJS Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

gruntjs/grunt-contrib-jshint has 700+ stars and 150+ forks on GitHub, is written in JavaScript, and was last pushed on Jun 21, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 34 minutes ago
Added to GitGenius on October 15th, 2026
Created on October 3rd, 2012
Open Issues & Pull Requests: 24 (+0)
GitHub issues: Enabled
Number of forks: 187
Total Stargazers: 702 (+0)
Total Subscribers: 22 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 40.6 days
Mean response time: 40.6 days
90th percentile: 40.6 days
Tracked items: 1

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

grunt-contrib-jshint is a Grunt plugin that validates JavaScript files with JSHint.

The plugin solves the problem of integrating static JavaScript linting into a Grunt-based build workflow. It wraps JSHint functionality and passes configuration options directly to JSHint, allowing developers to enforce code quality standards as part of their build process. The tool supports standard JSHint options plus several additional configuration features: a globals map for declaring global variables, a jshintrc option to load configuration from `.jshintrc` files, file extension filtering, file and directory ignore lists, and customizable reporters for output formatting.

Projects using Grunt as their task runner should adopt this plugin when they need automated JavaScript validation in their build pipeline. It suits teams already invested in Grunt who want to enforce consistent code style without switching build systems. The plugin integrates seamlessly with Grunt's configuration and task execution model, allowing linting to run alongside other build tasks. Developers can choose between built-in JSHint reporters, external reporters, or write custom ones to match their output preferences. The force option enables non-blocking linting, useful when you want to report errors without failing the build.

The project maintains active test coverage through continuous integration workflows. Development activity shows consistent engagement with bug fixes and feature maintenance across multiple releases.