webhintio/hint

💡 A hinting engine for the web

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 18th, 2026
Created on February 16th, 2017
Open Issues & Pull Requests: 531 (+0)
GitHub issues: Enabled
Number of forks: 822
Total Stargazers: 3,703 (+0)
Total Subscribers: 73 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.7 days
Mean response time: 161.0 days
90th percentile: 428.0 days
Tracked items: 40

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 73
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 724 days
Stale 30+ days: 73
Stale 90+ days: 62

Recent activity

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

Top labels

  • type:bug (58)
  • area:browser-extension (15)
  • area:documentation (14)
  • type:new-feature (12)
  • hacktoberfest (5)
  • good first issue (4)
  • apprenticeship (3)
  • area:hint (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

webhint is a customizable linting tool that helps developers improve their websites across accessibility, performance, cross-browser compatibility, and security by identifying best practice violations and common errors.

The tool addresses the challenge of maintaining code quality across multiple dimensions of web development. It works by analyzing code against configurable rules called hints, which check for issues in accessibility, speed, interoperability, and security. The tool can be invoked from the command line, integrated into VS Code, or run as a browser extension, making it accessible at different points in a developer's workflow.

Developers should choose webhint if they want a unified linting solution that covers accessibility and performance alongside traditional code quality concerns. It suits projects where teams need flexibility in which rules to enforce, since the tool is designed to be customizable. The project is structured as a monorepo, meaning the CLI, extensions, hints, and formatters are all maintained together and published as separate packages, which allows developers to adopt only the components they need.

The project maintains active development across its multiple components, with ongoing work on the core linting engine, browser extension, and VS Code extension each tracked in their own contribution guidelines. The codebase is written in TypeScript and follows established governance structures including a charter and code of conduct aligned with the OpenJS Foundation.