Operations → Build & Packaging
Linting
Static analysis that checks source code for suspicious patterns, style violations, and likely defects without executing it.
Linting
Linting analyzes source code without executing it. A linter applies language-aware rules to detect likely bugs, unsafe constructs, inconsistent style, unused code, and maintainability problems early in the feedback loop.
What linting is good at
Linting is strongest for mechanically recognizable patterns: unreachable branches, suspicious equality checks, missing dependency declarations, formatting inconsistencies, and project-specific conventions. It makes code review more valuable by moving repetitive checks to automation.
Limits
A clean lint result does not prove correctness. Rules can produce false positives, and overly strict configurations can encourage suppression rather than understanding. Teams should keep rules explainable, versioned, fast, and automatically enforced in editors and CI.