57 repos across 3 sub-areas
Static analysis and linting tools for multiple programming languages, including language-specific linters like SwiftLint, pylint, Detekt, and ameba, as well as polyglot static analysis frameworks and orchestration platforms. The cluster spans implementations across Go, Python, and Rust, reflecting both the tools themselves and their underlying infrastructure for detecting code quality issues, security vulnerabilities, and style violations without executing code.
Static Analysis & Code Quality Tools
24 repos
Static analysis tools and linters that scan source code for bugs, style violations, and quality issues without executing it. The cluster spans multiple languages—Rust, Go, TypeScript, and Haskell are most common—reflecting the cross-language nature of the problem. Central projects like shellcheck, ameba, reviewdog, and qlty represent different approaches (shell script linting, Ruby analysis, CI integration, unified quality platforms), while many repos implement language-specific or general-purpose checkers and formatters.
Go linters and static analysis
22 repos
Tools for static code analysis and linting across Go and multiple other languages. The cluster centers on Go linters like revive and broader static analysis frameworks, alongside language-specific checkers for shell scripts (shellcheck), TypeScript, and Python. You'll find utilities for enforcing code quality, catching errors before runtime, and integrating analysis into development workflows—with particular strength in the Go ecosystem.
Static analysis and linting tools
11 repos
Tools and libraries for automatically detecting code quality issues, style violations, and potential bugs across multiple programming languages. The cluster spans language-specific linters like pylint and SwiftLint, language-agnostic linters like revive, and high-performance implementations like ruff (written in Rust). Visitors will find mature, production-ready linting frameworks primarily in Python and Go, along with supporting utilities for error naming and PEP8 compliance.