What is PHPStan?
It focuses on finding errors in your code without actually running it. It catches whole classes of bugs even before you write tests for the code. It moves PHP closer to compiled languages in the sense that the correctness of each line of the code can be checked before you run the actual line.
PHPStan is a tool in the Code Review category of a tech stack.
PHPStan is an open source tool with 12.2K GitHub stars and 900 GitHub forks. Here’s a link to PHPStan's open source repository on GitHub
Who uses PHPStan?
Companies
45 companies reportedly use PHPStan in their tech stacks, including Ornikar, Extensions, and Connect.club.
Developers
76 developers on StackShare have stated that they use PHPStan.
PHPStan Integrations
PHP, WordPress, Laravel, Drupal, and Symfony are some of the popular tools that integrate with PHPStan. Here's a list of all 12 tools that integrate with PHPStan.
PHPStan's Features
- Static Analysis Tool
- Focuses on finding errors in your code without actually running it
- Extensible
PHPStan Alternatives & Comparisons
What are some alternatives to PHPStan?
SonarQube
SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
ESLint
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Prettier
Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary.
TSLint
An extensible static analysis tool that checks TypeScript code for readability, maintainability, and functionality errors. It is widely supported across modern editors & build systems and can be customized with your own lint rules, configurations, and formatters.
Stylelint
A mighty, modern CSS linter that helps you enforce consistent conventions and avoid errors in your stylesheets.
