Linting
Definition
Linting analyzes source code statically for defined errors, style issues, or suspicious patterns.
A linter typically does not execute code but checks syntax trees, type information, or rules. It complements tests and security scanning but does not replace them.
Simply explained
Like an automatic spell and rule checker for code.
Why it matters in practice
Relevant for code quality, consistency, and early error detection.
Example from business
CI blocks a merge on TypeScript errors or forbidden patterns.
Limits and pitfalls
- Equating lint errors with functional tests; enabling thousands of rules without benefit; permanently ignoring warnings.
Origin & history
Static code checks have existed since early compiler/Unix tools; “lint” traces back to a Unix C analysis program from the 1970s.
Use in mid-sized companies
- Possible application in SMEs: integrate linting as a fast quality gate in local development and CI.
Frequently asked questions
Does a linter find all bugs?
No. Does it execute code? Usually not.
Sources
- Core Concepts · ESLint, Core Concepts
Sources checked on 12.10.2026.
Editorially reviewed on: