A
PHP_CodeSniffer
68.3
10,762 stars · BSD-3-Clause
Workflow Automation
Scrapling leads by 30.8 · decisive
A
68.3
10,762 stars · BSD-3-Clause
B · leads
99.1
103,871 stars · BSD-3-Clause
PHP_CodeSniffer versus Scrapling 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; Scrapling is written mainly in Python. The composite score is 68.3 for PHP_CodeSniffer and 99.1 for Scrapling.
Scrapling has 103,871 GitHub stars to PHP_CodeSniffer's 10,762, a gap of 93,109 (9.65×). Forks are 1,438 for PHP_CodeSniffer and 10,835 for Scrapling. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 78 versus 100.
Push history: PHP_CodeSniffer was last pushed on 01 April 2024 (959 days ago), and Scrapling was last pushed on 17 November 2026 (0 days ago). Open issues stand at 247 for PHP_CodeSniffer (0.023 per star) and 21 for Scrapling (0.000 per star). Issue-health scores are 70 and 96; activity scores are 16 and 100.
Both PHP_CodeSniffer and Scrapling are listed as BSD-3-Clause. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both PHP_CodeSniffer (10,762 stars) and Scrapling (103,871 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, Scrapling is open source.
Scrapling 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).
Scrapling finishes ahead at 99.1 against PHP_CodeSniffer at 68.3, a 30.8 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 | Scrapling |
|---|---|---|
| GitHub stars | 10,762 | 103,871 |
| Forks | 1,438 | 10,835 |
| Open issues | 247 | 21 |
| Adoption | 80 | 100 |
| Activity | 16 | 100 |
| Community | 78 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 68.3 | 99.1 |
PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards.
🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Scrapling has more GitHub stars: 103,871 versus 10,762 for PHP_CodeSniffer. The gap is 93,109 stars.
Scrapling 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 Scrapling 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. Scrapling 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Scrapling scores 99.1 and PHP_CodeSniffer scores 68.3. This page calls that a decisive lead for Scrapling.