awesome-repositories.com
Blog
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectAboutHow we rankPressMCP server
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
crate-ci avatar

crate-ci/typos

0
View on GitHub↗
4,002 stars·172 forks·Rust·Apache-2.0·6 views

Typos

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 filenames in addition to file content.

The system provides comprehensive text analysis capabilities, including pattern-based noise reduction to filter out technical strings like UUIDs, URLs, and hex codes. It supports automated code refactoring via in-place file mutation and integrates into development workflows through GitHub Actions, pre-commit hooks, and CI pipelines.

Analysis results can be exported in machine-readable JSON Lines or SARIF formats for integration with external security and quality tooling.

Features

  • Automated Typo Fixers - Automatically writes corrected spelling changes back to the local checkout to streamline typo fixing.
  • Code Spell Checkers - Scans programming language files to identify and correct spelling errors in comments, strings, and identifiers.
  • Spell Check Whitelisting - Supports the definition of valid words and patterns to ignore, effectively whitelisting terminology to reduce false positives.
  • Spell Checking Rules - Allows users to define specific typo-to-correction mappings and mark certain identifiers as always valid or invalid.
  • Dictionary-Based Validation - Validates text against locale-specific dictionaries to identify potential spelling errors in source code.
  • Automated Spelling Checkers - Scans repository files for typos during continuous integration workflows to identify errors in pull requests.
  • Custom Dictionary Managers - Provides a dictionary engine that integrates project-specific terminology and locale-specific word lists to expand the validation vocabulary.
  • Source Code Mutators - Automatically applies spelling corrections directly to source files on disk while preserving original formatting.
  • CI Pipeline Integrations - Integrates into CI pipelines to enforce spelling quality by setting failing exit codes when errors are found.
  • Continuous Integration Checks - Integrates automated spell checks into CI pipelines to prevent misspelled text from being merged into production.
  • Identifier Tokenizers - Decomposes camelCase and snake_case identifiers into individual words to detect spelling mistakes within code symbols.
  • Spelling Rule Configurations - Enables detailed customization of the spell-checking engine, including locale definitions and identifier handling rules.
  • Technical String Filters - Uses regular expressions to filter out technical strings like UUIDs, URLs, and hex codes to reduce false positives.
  • Analysis File Exclusions - Prevents specific files or file types from being scanned for typos based on glob patterns or content types.
  • Automated Code Refactoring - Automatically applies spelling corrections across the codebase to maintain professional naming and documentation.
  • Automated Fixers - Automatically writes corrected spelling changes directly back to source files within a local checkout.
  • Scan Scope Restrictions - Limits the scan scope by excluding hidden directories, version control paths, and specific files.
  • File Exclusion Patterns - Filters the scanning scope using glob patterns and gitignore rules to exclude specific files and directories.
  • File Exclusion Rules - Defines which files or directories to skip using exclusion lists, negation patterns, and forced-exclude flags.
  • Pre-commit Hooks - Executes spell checks as a pre-commit git hook to prevent misspelled text from entering the repository.
  • TOML Configuration Support - Uses TOML manifest files to manage tool settings and custom project-specific word lists.
  • Technical String Filters - The tool ignores emails, URLs, hex strings, and UUIDs to ensure only human-readable text is checked for errors.
  • False Positive Filtering - Filters out technical noise like UUIDs, SHAs, and JWT tokens to reduce false positive spell-check alerts.
  • GitHub Actions - Provides native support for GitHub Actions, including code annotations and optimized pull request scanning.
  • SARIF Integrations - Generates reports in the Static Analysis Results Interchange Format for seamless integration with security and quality tooling.
  • Static Analysis Exporters - Exports detected typos in SARIF and JSON formats for integration with external security and quality tooling.
  • Developer Tools - Source code spell checker.
  • Development Tools - Fast source code spell checker.

Star history

Star history chart for crate-ci/typosStar history chart for crate-ci/typos

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Frequently asked questions

What does crate-ci/typos do?

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.

What are the main features of crate-ci/typos?

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.

What are some open-source alternatives to crate-ci/typos?

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,…

Open-source alternatives to Typos

Similar open-source projects, ranked by how many features they share with Typos.
  • streetsidesoftware/vscode-spell-checkerstreetsidesoftware avatar

    streetsidesoftware/vscode-spell-checker

    1,664View on GitHub↗

    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

    TypeScript
    View on GitHub↗1,664
  • j178/prekj178 avatar

    j178/prek

    6,297View on GitHub↗

    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

    Rustgitgit-hookspre-commit
    View on GitHub↗6,297
  • ansible/ansible-lintansible avatar

    ansible/ansible-lint

    3,876View on GitHub↗

    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

    Pythonansibleansible-dev-toolsansible-lint
    View on GitHub↗3,876
  • pycqa/pylintPyCQA avatar

    PyCQA/pylint

    5,685View on GitHub↗

    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

    Python
    View on GitHub↗5,685
See all 30 alternatives to Typos→