Open-Source Testing · php-censor

php-censor

PHP Censor is a self-hosted continuous integration server for PHP projects, allowing teams to automate testing and code quality checks without relying on third-party SaaS. It supports multiple source control systems, databases, and testing frameworks with a straightforward YAML-based configuration.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/php-censor/php-censor

687

GitHub stars

145

Forks

PHP

Primary language

BSD-2-Clause

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	php-censor/php-censor
Owner	php-censor
Primary language	PHP
License	BSD-2-Clause — OSI-approved
Stars	687
Forks	145
Open issues	23
Latest release	2.1.6 (2025-03-15)
Last updated	2026-05-31
Source	https://github.com/php-censor/php-censor

What php-censor is

A BSD-licensed PHP 7.4+ CI/CD platform that orchestrates build pipelines via Beanstalkd queues, integrating with Git/Hg/SVN repositories and offering plugins for PHPUnit, Composer, database setup, and code analysis tools (PHPCS, PHPMessDetector, etc.). Requires Unix-like OS, web server, database backend, and shell execution capabilities.

Quickstart

Get the php-censor source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/php-censor/php-censor.git2cd php-censor3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Small to mid-size PHP teams needing self-hosted CI

Organizations that cannot or prefer not to use SaaS CI platforms (Jenkins, GitLab CI, GitHub Actions) and have in-house infrastructure. Particularly suited for teams with existing PHP codebases and a need for zero configuration or `.php-censor.yml` driven setups.

Multi-framework PHP testing in controlled environments

Projects requiring simultaneous execution of PHPUnit, Behat, Codeception, and PHPSpec tests alongside database (MySQL, PostgreSQL, SQLite) provisioning and teardown per build, all within a private network.

Compliance-driven deployments with audit trails

Regulated environments where CI logs, build artifacts, and deployment history must remain on-premises and under full organizational control, with no third-party data egress.

Implementation considerations

Requires Unix-like OS, PHP 7.4+, web server (Nginx/Apache2), relational database (MySQL/MariaDB/PostgreSQL), and Beanstalkd queue service. All must be provisioned and maintained in-house.
Shell execution functions (`exec()`, `shell_exec()`, `proc_open()`) must be enabled in PHP; assess security implications in your environment (privilege isolation, input sanitization).
Configuration can be fully automated via `.php-censor.yml` per repository or overridden in the web UI; plan rollout strategy for teams unfamiliar with CI configuration syntax.
Database migrations must be run manually after upgrades (`./bin/console php-censor-migrations:migrate`); plan downtime windows and test migrations in non-production first.
Beanstalkd dependency introduces operational complexity; requires monitoring, backup, and recovery planning as a critical service component.

When to avoid it — and what to weigh

Windows-only infrastructure — PHP Censor explicitly does not support Windows. Deployment requires Unix-like OS (Linux, BSD, macOS).
Need for managed SaaS simplicity — If team lacks DevOps resources or prefers minimal operational overhead, managed solutions (GitHub Actions, GitLab CI, CircleCI) offer better onboarding and support.
Bleeding-edge feature velocity expected — Currently on v2.1.6 (latest stable); v2.2 is WIP. Older major versions (1.0–1.3) are unsupported. Feature release cadence is moderate; projects needing cutting-edge CI features may find updates infrequent.
Large enterprise with existing CI/CD ecosystems — Requires Beanstalkd queue, dedicated database, and manual scaling. Not designed for high-concurrency or multi-tenant cloud deployments; integration with mature enterprise CI/CD toolchains may be difficult.

License & commercial use

Licensed under BSD-2-Clause (BSD 2-Clause Simplified License), a permissive OSI-approved license that allows commercial use, modification, and distribution with minimal restrictions (retain copyright/license notice, no warranty).

BSD-2-Clause is a permissive license compatible with commercial use. You may use, modify, and redistribute PHP Censor in commercial products and services. However, the license includes no warranty or liability protection; treat as-is regarding support and security updates. No commercial support or SLA is documented in the provided data; verify support arrangements separately.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	High
DEV.co fit	Good
Assessment confidence	High

Security considerations

Shell execution is enabled by design (`exec()`, `shell_exec()`, `proc_open()`). Build scripts have access to system commands; assume build environment is privileged. No mention of sandboxing, secret management patterns, or CI-specific security scanning in provided data. Assess: repository webhook validation, user authentication/authorization scopes, and build-time credential exposure in logs. Requires review of actual codebase and deployment documentation for security posture.

Alternatives to consider

Jenkins

Mature, widely-adopted open-source CI/CD with extensive plugin ecosystem, better scaling, and enterprise support. Higher operational overhead but more flexible for complex pipelines.

GitLab CI (self-hosted or SaaS)

Built-in CI/CD with Git integration, modern YAML pipelines, container-native support, and strong security features. SaaS option removes infrastructure overhead; self-hosted option offers control.

GitHub Actions

Tightly integrated with GitHub repositories, minimal setup, generous free tier, and ecosystem of pre-built actions. No self-hosting option, but simplest for GitHub-centric teams.

Software development agency

Build on php-censor with DEV.co software developers

Assess your infrastructure requirements and integration needs. Consult our team to design a self-hosted CI/CD solution tailored to your PHP platform.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

phpstan infection phpat

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Testing DevOps & CI/CD Infrastructure API Development & Integration Talk to DEV.co

php-censor FAQ

Can PHP Censor run on Windows?

No. Windows is explicitly not supported. Deployment requires Unix-like OS (Linux, BSD, macOS).

What PHP versions are supported?

Current stable (v2.1) and WIP (v2.2) require PHP 7.4+. Older major versions (1.0–1.3) are unsupported and required PHP 5.6–7.x.

Is commercial support available?

Not documented in the provided data. Project is community-maintained under BSD-2-Clause license. Verify support channels (GitHub issues, community forums) independently.

How are secrets (API keys, database passwords) handled?

No secret management documentation provided. Likely managed via environment variables or CI configuration files. Requires review of security best practices before production use.

Custom software development services

DEV.co helps companies turn open-source tools like php-censor into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source testing stack.

Ready to Deploy PHP Censor?

Assess your infrastructure requirements and integration needs. Consult our team to design a self-hosted CI/CD solution tailored to your PHP platform.

Talk to DEV.co Schedule a Consultation