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 main features of crate-ci/typos are: Automated Typo Fixers, Code Spell Checkers, Spell Check Whitelisting, Spell Checking Rules, Dictionary-Based Validation, Automated Spelling Checkers, Custom Dictionary Managers, Source Code Mutators.
Open-source alternatives to crate-ci/typos include: streetsidesoftware/vscode-spell-checker — This project is an integrated spelling validation tool designed for source code and documentation. It functions as an… j178/prek — Prek is a Git hook manager written in Rust that runs configured hooks as a single binary without requiring Python or… ansible/ansible-lint — ansible-lint is a static code analysis tool and linter designed to identify syntax errors and best practice violations… pycqa/pylint — Pylint is a static code analysis tool for Python that checks source code for errors, coding standard violations, and… include-what-you-use/include-what-you-use — Include What You Use is a C++ include optimizer and header dependency analyzer. It identifies unused or missing header… facebook/pyrefly — Pyrefly is a static type checker for Python that operates as a language server, delivering real-time diagnostics,…
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
Prek is a Git hook manager written in Rust that runs configured hooks as a single binary without requiring Python or other external runtimes. It executes hooks faster than standard tools through parallel processing and bundled Rust implementations, and includes a built-in hook repository that enables fully offline operation without network access or environment setup. The tool supports both TOML and YAML configuration formats with identical semantics, and can run hooks from existing pre-commit configuration files without modification. Prek distinguishes itself through workspace-aware monorepo
ansible-lint is a static code analysis tool and linter designed to identify syntax errors and best practice violations within Ansible playbooks and roles. It functions as a quality gate for automation pipelines, scanning configuration files and scripts without executing the code to ensure reliability and consistency. The project distinguishes itself by acting as an automated code formatter that can correct identified linting issues and reformat files to meet community standards. It also serves as a dependency manager, automatically detecting and installing required roles and collections from
Pylint is a static code analysis tool for Python that checks source code for errors, coding standard violations, and code smells without executing the program. It parses code into an abstract syntax tree and walks the tree to detect issues, enforces configurable style rules and naming conventions, and identifies duplicate code blocks by comparing tokenised source sequences. The tool also includes an inference engine that deduces variable types by simulating code paths, enabling deeper analysis even in untyped code. What distinguishes Pylint is its plugin-based checker architecture, which allo