A · leads
paperclip
94.7
114,484 stars · MIT
Workflow Automation
paperclip leads by 14.0 · clear
A · leads
94.7
114,484 stars · MIT
B
80.7
12,635 stars · Apache-2.0
paperclip versus posting 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; posting is written mainly in Go. The composite score is 94.7 for paperclip and 80.7 for posting.
paperclip has 114,484 GitHub stars to posting's 12,635, a gap of 101,849 (9.06×). Forks are 18,987 for paperclip and 296 for posting. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 58.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and posting was last pushed on 16 October 2026 (32 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 87 for posting (0.007 per star). Issue-health scores are 52 and 84; activity scores are 100 and 78.
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. posting 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 paperclip and 96 for posting. This is a procurement signal, not legal advice.
In Workflow Automation, both paperclip (114,484 stars) and posting (12,635 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, posting is open source.
The lead is split. paperclip is furthest ahead on fork community (100 to 58), while posting is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against posting at 80.7, a 14.0 point clear 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 | posting |
|---|---|---|
| GitHub stars | 114,484 | 12,635 |
| Forks | 18,987 | 296 |
| Open issues | 6,806 | 87 |
| Adoption | 100 | 81 |
| Activity | 100 | 78 |
| Community | 100 | 58 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 80.7 |
The open-source app everyone uses to manage agents at work
The modern API client that lives in your terminal.
paperclip has more GitHub stars: 114,484 versus 12,635 for posting. The gap is 101,849 stars.
paperclip was pushed more recently: 17 November 2026 versus 16 October 2026 for posting. That is 32 days apart.
Yes. This catalog marks both paperclip and posting 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. posting 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.
paperclip scores 94.7 and posting scores 80.7. This page calls that a clear lead for paperclip.