A
PHP_CodeSniffer
68.6
10,762 stars · BSD-3-Clause
Workflow Automation
puppeteer leads by 30.5 · decisive
A
68.6
10,762 stars · BSD-3-Clause
B · leads
99.1
95,849 stars · Apache-2.0
PHP_CodeSniffer versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. PHP_CodeSniffer is written mainly in PHP; puppeteer is written mainly in TypeScript. The composite score is 68.6 for PHP_CodeSniffer and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to PHP_CodeSniffer's 10,762, a gap of 85,087 (8.91×). Forks are 1,438 for PHP_CodeSniffer and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 79 versus 100.
Push history: PHP_CodeSniffer was last pushed on 01 April 2024 (959 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 247 for PHP_CodeSniffer (0.023 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; activity scores are 16 and 100.
PHP_CodeSniffer is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. puppeteer is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for PHP_CodeSniffer and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both PHP_CodeSniffer (10,762 stars) and puppeteer (95,849 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: PHP_CodeSniffer is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 84 points (16 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against PHP_CodeSniffer at 68.6, a 30.5 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | PHP_CodeSniffer | puppeteer |
|---|---|---|
| GitHub stars | 10,762 | 95,849 |
| Forks | 1,438 | 9,607 |
| Open issues | 247 | 201 |
| Adoption | 81 | 100 |
| Activity | 16 | 100 |
| Community | 79 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 68.6 | 99.1 |
PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 10,762 for PHP_CodeSniffer. The gap is 85,087 stars.
puppeteer was pushed more recently: 17 November 2026 versus 01 April 2024 for PHP_CodeSniffer. That is 959 days apart.
Yes. This catalog marks both PHP_CodeSniffer and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
PHP_CodeSniffer is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. puppeteer is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 99.1 and PHP_CodeSniffer scores 68.6. This page calls that a decisive lead for puppeteer.