php-censor: seven release lines, a queue daemon, and a hard-coded composer path
PHP Censor is an open source self-hosted continuous integration server for PHP projects.
At a glance
- What is it?
- php-censor/php-censor is a self-hosted PHP CI server forked from PHPCI, needing a Unix host with three shell functions enabled, a database, and Beanstalkd, while its Makefile defaults to PHP 7.4 and points at a Composer binary in /usr/local/bin.
- Who is it for?
- PHP Censor earns its place if you need CI for PHP that runs on your own hardware and cannot leave the network, and the feature surface is still wide: five test frameworks, a long plugin list, six notification targets, and LDAP for authentication. Four things to weigh before you deploy it.
- Can I use it commercially?
- Yes. BSD-2-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly PHP, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- php-censor/php-censor687 ★ · +0
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| php-censor/php-censor | 687 | 687 |
0 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Three shell functions and a queue daemon stand between you and a build
The system requirements list is short and unforgiving. A Unix-like OS, with Windows stated as not supported rather than as unsupported. PHP 7.4 or newer, built with OpenSSL support, and with `exec()`, `shell_exec()`, and `proc_open()` enabled, which on a hardened host or a shared plan are frequently switched off. A web server, named as Nginx or Apache2. A database, MySQL or MariaDB or PostgreSQL. And a Beanstalkd queue, which is the piece most self-hosted CI substitutes never mention. That last item is not decorative: it is what stands between a build request and the worker that runs it, and the Makefile has a `run-worker` target that starts `bin/console php-censor:worker -v`. You are not installing a web app, you are installing a web app plus a separate long-running process. The database is something the server also acts on rather than only reads from, since plugins exist to set up and tear down test databases for PostgreSQL, MySQL, and SQLite as part of a build. That is how a migration gets exercised on every commit instead of once a quarter by hand.
Seven release lines, four unsupported, one still a work in progress
The version table at the top of the documentation is the most useful page in the repository. Each line has a name, which is a Rick and Morty character for the 1.x and 2.x series. `1.0` Morty Smith is at `1.0.16` on `release-1.0` and marked UNSUPPORTED, `1.1` Birdperson at `1.1.6`, `1.2` Summer Smith at `1.2.4`, and `1.3` Jerry Smith at `1.3.7`, all unsupported, and all four requiring PHP `>=5.6, <8.0`. Then `2.0` Rick Sanchez at `2.0.14` on `release-2.0`, labelled the last stable version with an upgrade guide from v1 to v2, and `2.1` Mr. Meeseeks at `2.1.6` on `release-2.1`, labelled the current stable version. Both of those need PHP `>=7.4`. The default branch `master` is not a stable branch at all, it carries `2.2`, marked as the feature minor version and WIP.
Two releases were cut 28 minutes apart on the same afternoon
The release dates are worth a sentence of their own because they explain the branch structure. Version `2.0.14`, named Rick Sanchez, was published at 17:09:35 on 2025-03-15. Version `2.1.6`, named Mr. Meeseeks, was published at 17:38:06 the same day, twenty-eight minutes later. Before that, `2.1.5` dates from 2024-05-04. So the maintenance line and the current stable line were both updated in one sitting, which is the expected shape of a project that maintains a backport branch, and it also means a fresh install lands on code whose tag is over a year older than the branch it was cut from. The last push to `master` is 2026-05-31, so the 2.2 feature line has been accumulating for over a year without cutting a stable release.
The Makefile points at /usr/local/bin/composer and defaults to PHP 7.4
Two lines at the top of the Makefile decide how much trouble you will have:
PHP?=php7.4
COMPOSER=/usr/local/bin/composer`PHP` is overridable, and the help text says so, offering `make install PHP=php8.0` as the example. `COMPOSER` is not: it is a plain assignment pointing at an absolute path inside `/usr/local/bin`, which is where a Homebrew or manual Composer install lands on some macOS setups and nowhere else. On a Linux box installed through a distribution package, on a PHP version manager, or in a container, that path does not exist and every target that uses it fails. The dependency target also has an asymmetry worth knowing: `install` is guarded by `if [ ! -d "vendor" ]`, so a stale or half-populated `vendor/` directory is skipped rather than repaired, and `install-force` exists to do the unconditional version. The rest of the file is a clean target list, and the default goal is `list`.
Project config can arrive from three places and the web UI wins
There are three routes, and the precedence is stated rather than implied. You can add a project with no configuration at all, in which case a set of zero-config plugins runs: Composer, TechnicalDebt, PHPLoc, PHPCpd, PHPCodeSniffer, PHPMessDetector, PHPDocblockChecker, PHPParallelLint, PHPUnit, and Codeception. You can add a `.php-censor.yml` to the root of your repository, which the documentation compares to how Travis CI works. Or you can configure the project on the PHP Censor project page, and that option explicitly cancels the file config from your repository. The file format mirrors the build phases:
setup:
composer:
action: "install"
directory: "."
test:
php_unit:
config: "phpunit.xml"
php_mess_detector:
allow_failures: true
php_code_sniffer:
standard: "PSR2"
php_cpd:
allow_failures: true
complete:
email_notify:
default_mailto_address: [email protected]Two of the checks are set to `allow_failures: true` in the example, which is a hint about how strict the defaults are. The project dogfoods the file route: `.php-censor.yml` is present at the root of the PHP Censor repository itself.
Four static analysis configs and a mutation testing target
The root directory carries more analysis configuration than most PHP projects of any size. There is `.php-cs-fixer.dist.php` for formatting, `psalm.xml.dist` for static analysis, `rector.php` for automated refactoring, `infection.json.dist` for mutation testing, `phpmd.xml.dist` for mess detection, `phpunit.xml.dist` for the test runner, and `codecov.yml` for coverage reporting. A separate `VERSION.md` at the root holds the version outside the Composer metadata, and the prose documentation sits in `docs/en/` with its own pages for installing, updating, and configuring a project, per-source pages for GitHub, Bitbucket, GitLab, and Git, and a page per plugin, alongside `docs/UPGRADE_2.0.md` for the move off version 1 that the version table links to directly. The Makefile gives each of them a target. Psalm runs with `--threads=4 --show-snippet=true --show-info=true`. Rector runs in `--dry-run` mode with a separate `rector-fix` target for the write pass. Infection runs `vendor/bin/infection --threads=4 --show-mutations -vvv`. Migrations have their own console commands, `./bin/console php-censor-migrations:migrate` to apply and `./bin/console php-censor-migrations:create NewMigrationName` to author a new one. This is a project that takes its own build seriously, which is worth remembering when you compare it to the plugins it ships.
Phar tests skip themselves unless phar.readonly is off
Running the suite is one command:
./vendor/bin/phpunit --configuration ./phpunit.xml.dist --coverage-html ./tests/runtime/coverage -vvv --colors=alwaysTwo documented conditions will otherwise make a green run misleading. The Phar plugin tests require the `phar.readonly` setting to be turned Off in `php.ini`, and without it those tests are skipped rather than failed, so you get a passing suite that covered less than you think. Database tests need empty databases created on localhost with a user and password for MySQL and PostgreSQL, and the connection details passed as environment variables read from `phpunit.xml.dist`: `SKIP_DB_TESTS`, `POSTGRESQL_DBNAME`, `POSTGRESQL_USER`, `POSTGRESQL_PASSWORD`, `MYSQL_DBNAME`, `MYSQL_USER`, and `MYSQL_PASSWORD`. A CI box that has databases but not the variables will report the same result as one that has neither.
The plugin list reaches IRC and XMPP, and that is the point
Read the feature list as an inventory of what PHP tooling looked like when this fork was taken. Test runners cover PHPUnit, Atoum, Behat, Codeception, and PHPSpec. Static and style checks cover Lint, PHPParallelLint, Pdepend, PHPCodeSniffer, PHPCpd, PHPCsFixer, PHPDocblockChecker, PHPLoc, PHPMessDetector, PHPTalLint, and TechnicalDebt. Build steps include Campfire, CleanBuild, CopyBuild, Deployer, Env, Git, Grunt, Gulp, PackageBuild, Phar, Phing, Shell, and Wipe. Notification targets are Email, XMPP, Slack, IRC, Flowdock, and Telegram, and authentication can be delegated to an LDAP server. Source checkout reaches GitHub, Bitbucket over both Git and Hg, GitLab, plain Git, Mercurial, SVN, and a local directory. For a legacy codebase on an old build stack, that list is the argument for using this rather than a hosted runner that has dropped support for the tools you still depend on.
Editorial conclusion
PHP Censor earns its place if you need CI for PHP that runs on your own hardware and cannot leave the network, and the feature surface is still wide: five test frameworks, a long plugin list, six notification targets, and LDAP for authentication. Four things to weigh before you deploy it. It is a fork, so upstream PHPCI history and any patches you find there are one merge away. Windows is out, and three disabled PHP functions will block it on locked-down hosting. The build tooling around it assumes a specific machine, since the Makefile defaults to `php7.4` and calls Composer through an absolute path in `/usr/local/bin`. And the plugin list is a snapshot of a particular era of PHP tooling, which is a strength for legacy projects and a liability for new ones. Decide which of those four matters to you before you commit.
Frequently asked questions
What are the system requirements for PHP Censor?
A Unix-like OS, since Windows is stated as not supported, PHP 7.4 or newer with OpenSSL support and `exec()`, `shell_exec()`, and `proc_open()` enabled, a web server such as Nginx or Apache2, a MySQL/MariaDB or PostgreSQL database, and a Beanstalkd queue.
Which PHP Censor version should I install?
The version table marks `2.1.6` on the `release-2.1` branch as the current stable version and `2.0.14` on `release-2.0` as the last stable one, while `master` carries `2.2` as a work in progress. The `1.0` through `1.3` lines are all marked unsupported and require PHP `>=5.6, <8.0`.
How do I configure a project in PHP Censor?
Three ways. Add the project with no config and let the zero-config plugins run, add a `.php-censor.yml` to the repository root in the Travis CI style, or set the config on the PHP Censor project page, which cancels any file-based config from your repository.
How do I run the PHP Censor test suite?
With `./vendor/bin/phpunit --configuration ./phpunit.xml.dist --coverage-html ./tests/runtime/coverage -vvv --colors=always`, or `make test`. Phar plugin tests are skipped unless `phar.readonly` is set to Off in php.ini, and database tests need empty databases plus environment variables from `phpunit.xml.dist`.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/php-censor-php-censor)Star history chart for your README
[](https://hysenlabs.com/projects/php-censor-php-censor)Was this useful?