Brief History of Tools Watching and Changing Your PHP Code

This post was updated at December 2020 with fresh know-how.
What is new?

Removed deprecated and unused tools, to keep focus on relevant ones.

From coding standard tools, over static analysis to instant upgrade tools. This post is going to be a geeky history trip. Which tool was first? How they build on shoulders of each other?

1. Coding Standard Tools

PHP_CodeSniffer from Australia

Tokens Modifies Code

The first tool that made it to the mainstream of coding standard tools was created around 2007 by Greg Sherwood from Australia. At least by date of the oldest post I could found.

Greg has been maintaining the repository for last 11 years (at least). I don't know anyone else who would take care of his project for such a long time without stepping back - much respect!

PHP CS Fixer from Symfony

Tokens Modifies Code

Reporting errors are helpful, but fixing them for you is even more helpful. More people got a similar need and around Symfony 2.0 times and 2011 next tools were born - PHP CS Fixer.

The first version was created by Fabien Potentier, author and founder of Symfony, and it used mostly regular expressions.

The decision to fix everything by default was the huge jump in history of these tools. It was the first case of a tool that would be so bold to change your code for you. You had to believe it, you had to overcome the fear of modifying it the wrong way or even deleting. I mean, now we're used to it like to cars, but at one point of history, they were just riding bombs.

With PHP CS Fixer 1.0 release in 2014 and rising popularity of automated fixes was big motivation for PHP_CodeSniffer to add similar feature - code beautifier - to version 2.

It also helped with another issue. The development of PHP_CodeSniffer 2.8 and later almost froze to zero. I remember because I started working on EasyCodingStandard right between PHP_CodeSniffer 2.8 and 3.0 (depending on 3.0-dev), which took 14 uncertain months.

So PHP_CodeSniffer now holds Modifies Code as well.

Both use token_get_all() that basically parses code to strings. Do you want to know how they actually work?

EasyCodingStandard from the Czech Republic

Tokens Modifies Code

I saw many projects that use both tools, yet very poorly - because split attention divides the focus in the same ratio. The mission of this tool is to help new generations to adopt coding standard with almost no effort. So in 2016 the EasyCodingStandard was born.

2. Static Analysis Tools



This package is barely known for code analysis. But it provides the technology that all the other tool builds on - abstract syntax tree (known as AST).

It all started as a question on StackOverflow - Any decent PHP parser written in PHP? nikic answered himself with a php-parser less than a 6 months later.

I would not write this post and neither have my fuel for passion without this tool, so huge thank you, Nikita, for creating it and maintaining it.

All following tools use an AST analyzer - that's how they know what object is $object variable, like in this example:


class SomeObject
    public function exist()

$object = new SomeObject; // AST remembers that "$object" is "SomeObject" type
$object->missing(); // here we know that "missing" does not exist in "SomeObject"

PHPStan by Ondrej Mirtes

AST * 2016

If you don't use any static analysis tool, give PHPStan a try. I've made minimalist intro that will help you with first steps . It's worth investing even day or two to set it up because these tools will join toolkit of everyday use, like Composer or PHPUnit.

vimeo/psalm by Matthew Brown

AST * 2016 Modifies Code

Psalm is a very interesting tool that was born to fight Vimeo code complexity. It was the first tool from this group of 3, that started fixing the code.

3. Deprecation Detectors

This group is widely used in the framework-agnostic PHP community.



This tool checks for PHP cross-version compatibility. It allows you to analyze your code for compatibility with higher and lower versions of PHP.

It's useful to know what places are wrong, but you still have to fix them all manually.

4. Instant Upgrade Tools


Tokens Modifies Code Deprecated

This tool was created in 2015 and it's revolutionary. Why? It wisely connects the token analysis of PHP CS Fixer with deprecations in Symfony 2 to 3. Imagine it like PHP CS Fixer + sensiolabs-de/deprecation-detector working for you.

Isn't that amazing? You just sit, run this tool and send invoices. Genius! The features are limited due to Tokens, but still, I love this.


AST Modifies Code

It's 2017 and Rector still had to wait many months to be born. For what?

Well, it's built on php-parser and as it modifies the code and prints it back, it needed to keep spacing. That's one of AST drawbacks - it doesn't care about all that coding standards spacings.

They say "history repeats", but I never trusted that. Until I saw that similar need Fabien had while making the PHP CS Fixer in 2012 - Optionally add nodes for whitespace. More people wanted AST-based coding standards:

php-parser 4.0-dev already had this feature, so Rector ran on it since the very start. It was not until February 2018 when it was finally released.

Last giant Rector builds on is the one for type analysis - PHPStan. Thanks to that, it doesn't reinvent the wheel and can focus on the refactoring part.

And that's a brief history of big-brother tools that watch your code and modify it for you.

Do you learn from my contents or use open-souce packages like Rector every day?
Consider supporting it on GitHub Sponsors. I'd really appreciate it!