SECAI Core · phase 12 of 15 · noun
Code linting
A process where an AI tool provides recommendations for errors, bugs, and inconsistencies within code
The Explain card
- Plain English
- Linting is having an automated tool read your code and flag mistakes, risky constructs and inconsistencies before a human ever reviews it. AI-powered linters go further, suggesting fixes and explaining the problem.
- Example
- A developer writes a Python function that builds a database query by gluing strings together. The AI linter in the editor flags it as a likely SQL injection and suggests a parameterised query instead.
- Why it matters
- Most vulnerabilities start as ordinary bugs. Catching them at the keystroke, rather than in production, is the cheapest fix a defender will ever get, and AI lint can cover AI-specific mistakes too.
- Hook
- Lint is the fluff you remove before the fire starts.
Word knowledge
How the word is built, where it came from, and what it sits beside in memory.
In a sentence
The development pipeline runs code linting before deployment to flag unsafe syntax in the authentication module.
Why these words
- code Latin codex, book or set of laws, through French code identifies the written program text being examined
- linting English lint, loose fibers, adapted from the Unix tool lint names the act of using a linter
Where it came from
- Origin
- English computing phrase formed from code and linting, following the Unix program lint introduced in 1978
- Entered the language
- late 20th century
- What changed
- Lint first meant loose fibers, then gave its name to a program that detected small flaws in source code, producing the verb lint and noun linting.
How it is spelled
- Pattern
- Code keeps a silent final e that marks the long o sound.
- Pattern
- Linting adds -ing directly to lint because the final consonants form a cluster.
Spelled like
- mode
- node
- testing
- printing
Broken into chunks
-
code
- encode
- decode
-
lint
- linter
- lint-free
-
-ing
- testing
- scanning
What it sits beside
Same subject
- static analysis
- secure coding
- compiler warning
- source-code review
Same shape
- code review
- code testing
- code scanning
automated code checks
- code linting
- type checking
- dependency scanning
Where it sits in the deck
Phase 12: Defensive Technologies and Secure Development Practices
Map defences directly to the attacks just catalogued — the technical controls, secure coding practices, and protective tools that harden AI and traditional systems alike.