Skip to content
DevUtils Online

Workflow Automation

paperclip vs robotgo

paperclip leads by 8.4 · clear

A · leads

paperclip

94.7

114,484 stars · MIT

B

robotgo

86.3

10,907 stars · Apache-2.0

paperclip versus robotgo 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; robotgo is written mainly in Go. The composite score is 94.7 for paperclip and 86.3 for robotgo.

paperclip has 114,484 GitHub stars to robotgo's 10,907, a gap of 103,577 (10.50×). Forks are 18,987 for paperclip and 968 for robotgo. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 70.

Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and robotgo was last pushed on 13 November 2026 (4 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 4 for robotgo (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 92.

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. robotgo 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 robotgo. This is a procurement signal, not legal advice.

In Workflow Automation, both paperclip (114,484 stars) and robotgo (10,907 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, robotgo is open source.

The lead is split. paperclip is furthest ahead on fork community (100 to 70), while robotgo is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.

paperclip finishes ahead at 94.7 against robotgo at 86.3, a 8.4 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

paperclip versus robotgo metrics
Signal paperclip robotgo
GitHub stars 114,484 10,907
Forks 18,987 968
Open issues 6,806 4
Adoption 100 80
Activity 100 92
Community 100 70
Issue health 52 96
License 96 96
Self-hosting 100 100
Composite 94.7 86.3

Questions this page answers

Which has more GitHub stars, paperclip or robotgo?

paperclip has more GitHub stars: 114,484 versus 10,907 for robotgo. The gap is 103,577 stars.

Which was updated more recently, paperclip or robotgo?

paperclip was pushed more recently: 17 November 2026 versus 13 November 2026 for robotgo. That is 4 days apart.

Can I self-host both paperclip and robotgo?

Yes. This catalog marks both paperclip and robotgo as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, paperclip or robotgo?

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. robotgo 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.

Who wins the paperclip vs robotgo score?

paperclip scores 94.7 and robotgo scores 86.3. This page calls that a clear lead for paperclip.

Related comparisons