What does the term "static code analysis" mean?

Static code analysis is a method of checking a program without running it, where a tool analyzes the source code and finds potential errors, bugs, dangerous constructs, style violations, and other problems during development.

---

#What static analysis actually does

Static analysis tools:

• check the syntax and structure of the code,
• detect unused variables and imports,
• look for potential bugs (for example, references to nonexistent variables),
• track the use of dangerous or unwanted constructs,
• check compliance with the coding style (based on set rules),
• help maintain clean and consistent code.

---

#The key idea

The code is analyzed as text and a syntax tree (AST). Conclusions are drawn from the structure of the program, not from its behavior at runtime.

---

#Why it is used

Static analysis:

• prevents errors in advance, before the application even runs,
• reduces the cost of fixing bugs (they are easier to catch early),
• makes code more reliable, safer, and more understandable,
• helps teams maintain a consistent style and quality.

---

#Examples of tools

• for JS/TS - ESLint
• for Python - pylint
• for Java - Checkstyle, SpotBugs
• for security - SonarQube, Bandit

---

#Summary

Static analysis is an automatic check of source code without running it, which allows finding errors, vulnerabilities, and rule violations at an early stage.

In other words, static analysis is bug prevention and a means of maintaining high code quality in a project.