A · leads
paperclip
94.7
114,484 stars · MIT
Workflow Automation
paperclip leads by 27.2 · decisive
A · leads
94.7
114,484 stars · MIT
B
67.5
10,762 stars · BSD-3-Clause
paperclip versus PHP_CodeSniffer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. paperclip is written mainly in TypeScript; PHP_CodeSniffer is written mainly in PHP. The composite score is 94.7 for paperclip and 67.5 for PHP_CodeSniffer.
paperclip has 114,484 GitHub stars to PHP_CodeSniffer's 10,762, a gap of 103,722 (10.64×). Forks are 18,987 for paperclip and 1,438 for PHP_CodeSniffer. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 74.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and PHP_CodeSniffer was last pushed on 01 April 2024 (959 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 247 for PHP_CodeSniffer (0.023 per star). Issue-health scores are 52 and 70; activity scores are 100 and 16.
paperclip is listed as MIT, 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. 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. License scores in this pair are 96 for paperclip and 96 for PHP_CodeSniffer. This is a procurement signal, not legal advice.
In Workflow Automation, both paperclip (114,484 stars) and PHP_CodeSniffer (10,762 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: paperclip is open source, PHP_CodeSniffer is open source.
The lead is split. paperclip is furthest ahead on recent activity (100 to 16), while PHP_CodeSniffer is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against PHP_CodeSniffer at 67.5, a 27.2 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 | paperclip | PHP_CodeSniffer |
|---|---|---|
| GitHub stars | 114,484 | 10,762 |
| Forks | 18,987 | 1,438 |
| Open issues | 6,806 | 247 |
| Adoption | 100 | 80 |
| Activity | 100 | 16 |
| Community | 100 | 74 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 67.5 |
The open-source app everyone uses to manage agents at work
PHP_CodeSniffer tokenizes PHP files and detects violations of a defined set of coding standards.
paperclip has more GitHub stars: 114,484 versus 10,762 for PHP_CodeSniffer. The gap is 103,722 stars.
paperclip was pushed more recently: 17 November 2026 versus 01 April 2024 for PHP_CodeSniffer. That is 959 days apart.
Yes. This catalog marks both paperclip and PHP_CodeSniffer as self-hostable. Confirm each project's deploy docs before you plan a migration.
paperclip is listed as MIT, 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
paperclip scores 94.7 and PHP_CodeSniffer scores 67.5. This page calls that a decisive lead for paperclip.