For a spell checker for source code and comments, the strongest matches are automattic/harper (Harper is a local English-focused linter and grammar checker), crate-ci/typos (typos is a dedicated source code spell checker that) and streetsidesoftware/vscode-spell-checker (This VS Code extension checks spelling in comments, strings). languagetool-org/languagetool and feross/standard round out the shortlist. Each is ranked by relevance to your query, popularity and recent activity.
Automated tools that identify and correct spelling errors within programming source code and documentation comments.
Harper is a local English linter and grammar checker designed as an IDE writing assistant. It operates as a language server that provides real-time spelling and grammar analysis for markdown and code comments, processing all linguistic data on the local device to ensure privacy and eliminate cloud dependencies. The tool is specialized for technical documentation, featuring the ability to identify and ignore text within code fences and inline blocks to prevent false positives. It allows for personalized configuration through custom dictionaries and the use of suppression comments to exclude sp
Harper is a local English-focused linter and grammar checker that detects spelling issues in source code comments and documentation while correctly ignoring code blocks and inline syntax, offers custom dictionaries, and works as a language server for IDE integration — a solid fit for code proofreading, though limited to English and lacking explicit CI/CD or interactive fix features.
Typos is a source code spell checker and automated typo fixer designed to detect and correct spelling errors across programming languages and project files. It functions as a CI spelling validator and SARIF compatible linter, allowing projects to prevent misspelled text from reaching production. The tool features a customizable dictionary engine that utilizes TOML configuration and locale-specific dictionaries to manage project-specific terminology. It differentiates itself by splitting programming language identifiers into individual words for validation and verifying the spelling of filenam
typos is a dedicated source code spell checker that scans comments, strings, and documentation for spelling errors while ignoring code identifiers and syntax, directly addressing the core need, though its feature set (e.g., IDE plugins, markdown support) may be less comprehensive than some alternatives.
This project is an integrated spelling validation tool designed for source code and documentation. It functions as an editor extension that identifies and highlights spelling errors within comments, strings, and programming identifiers, providing real-time feedback and correction suggestions directly within the development environment. The tool distinguishes itself through its ability to parse complex naming conventions, such as camelCase and snake_case, into individual components for accurate validation. It operates as an offline-first engine, ensuring that all text analysis and dictionary l
This VS Code extension checks spelling in comments, strings, and documentation while ignoring code syntax, fitting the core need; it provides custom dictionaries and multi-language support but lacks built-in CI/CD integration, which keeps it from being the most comprehensive answer for automated pipelines.
LanguageTool is a multilingual grammar and style checking engine designed to detect spelling, grammar, and writing errors across multiple languages. It provides automated proofreading capabilities that can be deployed as a self-hosted server or executed as a standalone local desktop application. The project distinguishes itself through a flexible rule development framework, allowing linguistic patterns to be defined via XML or implemented as custom Java classes. It utilizes n-gram frequency modeling for confused word detection and supports neural word embeddings to improve disambiguation betw
LanguageTool is a general-purpose grammar and spell checker for natural language, not a tool that understands source code syntax or can selectively target comments and strings while ignoring identifiers.
Standard is a zero-configuration static analyzer, linter, and formatter for JavaScript. It functions as a style guide that enforces consistent coding rules and identifies programming errors without requiring manual configuration files. The tool distinguishes itself by providing an automatic code fixer that scans source files to correct style violations and ensure a uniform codebase. It implements a predefined rule set to eliminate the need for project-specific configuration. The project covers a broad range of static analysis capabilities, including support for experimental language syntax a
Standard is a JavaScript linter and code formatter that enforces coding style, not a spell checker for comments, strings, or documentation, so it does not detect spelling errors.
Pylint is a static code analyzer for Python that scans source code for errors, coding standard violations, code smells, and type-related issues without executing the program. It functions as a plugin-based linter framework, allowing users to extend its analysis capabilities with custom or third-party checks for project-specific rules and framework support. The tool also includes a duplicate code detector that identifies identical or near-identical code blocks across a project to help reduce redundancy. Beyond its core linting functionality, Pylint can generate UML class and package diagrams f
Pylint is a static code analyzer for Python that checks for errors, style violations, and code smells, but it does not detect spelling errors in comments, strings, or documentation, making it the wrong category of tool for your search.
TSLint is an extensible static analysis tool that checks TypeScript source files against a configurable set of lint rules. It scans code by walking the parsed TypeScript abstract syntax tree, applying rule objects to detect readability, maintainability, and functionality errors. The tool supports rule severity configuration, inline suppression through comment directives, and automatic attachment of fix objects for correcting violations. The project provides a framework for developing custom lint rules and formatters, allowing teams to enforce project-specific coding conventions beyond the bui
TSLint is a static analysis tool for enforcing TypeScript coding conventions and detecting code-quality issues, but it does not perform spell-checking in comments, strings, or documentation, so it is not the spell-checking tool this search describes.
danger-js is an automated code review tool and CI pipeline plugin that functions as a pull request linter. It verifies commit messages, tracks dependency changes, and ensures pull requests meet project standards by posting automated feedback and comments directly into the version control interface. The system integrates with various Git providers, including GitHub, GitLab, and BitBucket, to retrieve pull request metadata and execute custom review rules. It allows teams to package and distribute review conventions as shareable modules and supports the execution of rules written in transpiled l
danger-js is a CI-integrated code review automation tool that enforces project rules and conventions on pull requests, not a dedicated spell checker for source code comments and strings — it could be extended to run spelling checks, but its core purpose is broader pull request linting, not proofreading text in code.
Stylelint is a static code analysis tool and linter for CSS and style-like languages. It identifies errors, enforces coding conventions, and operates as a PostCSS plugin to validate stylesheets during build pipelines. The project distinguishes itself through support for non-standard syntaxes, including preprocessor parsing for SCSS and Less, and the ability to extract and lint embedded styles from JavaScript, HTML, and template literals. It features an automated fixing system that programmatically corrects repairable styling violations to ensure consistency. The system provides a plugin arch
stylelint is a CSS linter focused on enforcing style conventions and identifying syntax errors, not a spell-checking tool for comments, strings, or documentation, so it does not match the core capability of detecting spelling errors.