A fast, low-false-positive spell checker designed for source code and monorepos.
typos is a source code spell checker that identifies and corrects spelling mistakes within codebases. It is optimized for speed to handle large monorepos and minimizes false positives, making it safe to run in continuous integration pipelines like PR checks.
Developers and teams working on large codebases, especially those using monorepos, who need to automate spell checking in their CI/CD pipelines. It's also suitable for open-source maintainers who want to enforce spelling consistency in pull requests.
Developers choose typos over traditional spell checkers because it prioritizes accuracy with a curated list of known typo corrections, drastically reducing false positives. Its high performance and seamless integrations with tools like GitHub Actions and pre-commit hooks make it ideal for automated workflows.
Source code spell checker
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Optimized to scan entire monorepos efficiently, with benchmarks provided in the README, making it practical for large codebases.
Uses a curated list of known typo corrections, allowing it to run safely in CI pipelines like PR checks without manual intervention, as highlighted in the philosophy.
Supports custom ignore lists and rules via a `_typos.toml` file, enabling teams to exclude acronyms, names, or localized content with examples in the documentation.
Offers native support for GitHub Actions, pre-commit hooks, and provides JSON output and diff generation for custom scripts, as detailed in the integrations section.
Only corrects typos from its maintained list; unknown mistakes require manual configuration or contribution, which can lead to missed corrections in new or niche contexts.
Setting up custom ignore rules and file types involves editing TOML files, which can be complex and time-consuming for teams with diverse codebases.
Primarily designed for code spell checking; it may be less effective for prose-heavy documentation without additional configuration, as noted in the file type settings.