PHPackages                             foobugs-standards/php53to54 - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. foobugs-standards/php53to54

ActivePhpcs-standard

foobugs-standards/php53to54
===========================

PHP\_CodeSniffer standard for compatibility checking of PHP 5.3 to 5.4 migrations.

6681[26 issues](https://github.com/foobugs-standards/Php53to54/issues)[1 PRs](https://github.com/foobugs-standards/Php53to54/pulls)PHP

Since Apr 23Pushed 13y ago4 watchersCompare

[ Source](https://github.com/foobugs-standards/Php53to54)[ Packagist](https://packagist.org/packages/foobugs-standards/php53to54)[ RSS](/packages/foobugs-standards-php53to54/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

php53to54
=========

[](#php53to54)

php53to54 is a collection of sniffs for [PHP\_CodeSniffer](http://pear.php.net/PHP_CodeSniffer) that check an PHP 5.3 application for PHP 5.4 compatibility.

**This project is currently under development**

Features
--------

[](#features)

- Check for removed, deprecated or changed function, methods, constants etc. including stuff from removed or changed extensions
- Scan for usage of added, changed or removed parameters
- Search for removed ini-directives
- Namespace-aware scan for class, interface, constant definitions that would collide with new ones
- Check for invalid `break`/`continue` statements
- Check for call time pass by reference

[Detailed feature list](FEATURES.md).

Requirements
------------

[](#requirements)

- [PHP\_CodeSniffer 1.3.6+](http://pear.php.net/PHP_CodeSniffer)

Installation
------------

[](#installation)

Make sure you’ve PHP\_CodeSniffer installed. After that you can either put this standard into the PHP\_CodeSniffer Standards directory located in your PEAR directory: (`pear/PHP/CodeSniffer/Standards`) or place the standard somewhere else and use it as standalone standard.

### Composer

[](#composer)

You cann add the standard to your vendors directory by adding the dependency to your projects `composer.json`:

```
"require": {
	"foobugs-standards": "php53to54",
}

```

After an update with `composer update`, you’re able to include the standard via the full path using the `--standard` parameter:

```
vendor/bin/phpcs --standard="`pwd`/vendor/foobugs-standards/php53to54"

```

### Download

[](#download)

Download the [zip master](https://github.com/foobugs-standards/php53to54/archive/master.zip) from github and extract it in the PHP\_CodeSniffer Standards directory.

### Git-Clone-Install

[](#git-clone-install)

This script will go to your PHP\_CodeSniffer Standards directory and place a clone of php53to54 Standard inside of it:

```
cd `pear config-get php_dir`/PHP/CodeSniffer/Standards
git clone git@github.com:foobugs-standards/php53to54.git

```

Usage
-----

[](#usage)

### Installed standard

[](#installed-standard)

If you have this standard copied or cloned into the PHP\_CodeSniffer Standards directory the standard should be listed when calling:

```
phpcs -i

```

If `php53to54` is listed there you’re ready to use this standard on any directory:

```
phpcs --standard=php53to54

```

### External standard

[](#external-standard)

If you did not put the Standard into PHP\_CodeSniffers Standard directory you can specify the external location of the standard. Note that the path to the standard must be a full qualified path:

```
phpcs --standard=/Users/frank/Downloads/php53to54

```

You can find more options and arguments (f.i. ignoring files, extensions, memory limit) in the official [PHP\_CodeSniffer Manual](http://pear.php.net/manual/en/package.php.php-codesniffer.php).

Participate!
------------

[](#participate)

You can participate in this project by forking the [Repository](https://github.com/foobugs-standards/php53to54/) and push changes back to the project. Feel free to post issues or whishes in the [issue section](https://github.com/foobugs-standards/php53to54/issues).

###  Health Score

19

—

LowBetter than 10% of packages

Maintenance0

Infrequent updates — may be unmaintained

Popularity15

Limited adoption so far

Community13

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 98.1% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/2c0597339c399bea9497c59ad70ec933e5a6c95458122649baf2dab18038ba88?d=identicon)[goatherd](/maintainers/goatherd)

![](https://www.gravatar.com/avatar/680b6be4bd7dc29e90e6dcc8c3af152ca4cd60c6a3021fcff97fbbfb16e924be?d=identicon)[foobugs](/maintainers/foobugs)

---

Top Contributors

[![Ephigenia](https://avatars.githubusercontent.com/u/73654?v=4)](https://github.com/Ephigenia "Ephigenia (51 commits)")[![danez](https://avatars.githubusercontent.com/u/231804?v=4)](https://github.com/danez "danez (1 commits)")

### Embed Badge

![Health badge](/badges/foobugs-standards-php53to54/health.svg)

```
[![Health](https://phpackages.com/badges/foobugs-standards-php53to54/health.svg)](https://phpackages.com/packages/foobugs-standards-php53to54)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
