A · leads
paperclip
94.7
114,484 stars · MIT
Workflow Automation
paperclip leads by 6.2 · narrow
A · leads
94.7
114,484 stars · MIT
B
88.5
27,230 stars · MIT
paperclip versus vagrant 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; vagrant is written mainly in Ruby. The composite score is 94.7 for paperclip and 88.5 for vagrant.
paperclip has 114,484 GitHub stars to vagrant's 27,230, a gap of 87,254 (4.20×). Forks are 18,987 for paperclip and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 85.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 52 and 70; activity scores are 100 and 92.
Both paperclip and vagrant are listed as MIT. 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 paperclip (114,484 stars) and vagrant (27,230 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, vagrant is open source.
The lead is split. paperclip is furthest ahead on fork community (100 to 85), while vagrant is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against vagrant at 88.5, a 6.2 point narrow 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 | vagrant |
|---|---|---|
| GitHub stars | 114,484 | 27,230 |
| Forks | 18,987 | 4,491 |
| Open issues | 6,806 | 760 |
| Adoption | 100 | 88 |
| Activity | 100 | 92 |
| Community | 100 | 85 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 88.5 |
The open-source app everyone uses to manage agents at work
Vagrant is a tool for building and distributing development environments.
paperclip has more GitHub stars: 114,484 versus 27,230 for vagrant. The gap is 87,254 stars.
paperclip was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both paperclip and vagrant 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. vagrant 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
paperclip scores 94.7 and vagrant scores 88.5. This page calls that a narrow lead for paperclip.