Skip to content
DevUtils Online

Workflow Automation

cli vs nanobot

nanobot leads by 4.2 · narrow

A

cli

93.7

32,362 stars · Apache-2.0

B · leads

nanobot

97.9

50,147 stars · MIT

cli versus nanobot is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cli is written mainly in Rust; nanobot is written mainly in Python. The composite score is 93.7 for cli and 97.9 for nanobot.

nanobot has 50,147 GitHub stars to cli's 32,362, a gap of 17,785 (1.55×). Forks are 1,997 for cli and 8,755 for nanobot. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 84 versus 100.

Push history: cli was last pushed on 03 November 2026 (14 days ago), and nanobot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 137 for cli (0.004 per star) and 872 for nanobot (0.017 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.

cli 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. nanobot 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. License scores in this pair are 96 for cli and 96 for nanobot. This is a procurement signal, not legal advice.

In Workflow Automation, both cli (32,362 stars) and nanobot (50,147 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: cli is open source, nanobot is open source.

The lead is split. cli is furthest ahead on issue health (96 to 84), while nanobot is furthest ahead on fork community (100 to 84). Choose the dimension a rollout cannot compromise on.

nanobot finishes ahead at 97.9 against cli at 93.7, a 4.2 point narrow 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.

cli versus nanobot metrics
Signal cli nanobot
GitHub stars 32,362 50,147
Forks 1,997 8,755
Open issues 137 872
Adoption 96 100
Activity 92 100
Community 84 100
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 93.7 97.9

cli

Google Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. Includes AI agent skills.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cli or nanobot?

nanobot has more GitHub stars: 50,147 versus 32,362 for cli. The gap is 17,785 stars.

Which was updated more recently, cli or nanobot?

nanobot was pushed more recently: 17 November 2026 versus 03 November 2026 for cli. That is 14 days apart.

Can I self-host both cli and nanobot?

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

Which license is easier to embed in a commercial product, cli or nanobot?

cli 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. nanobot 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.

Who wins the cli vs nanobot score?

nanobot scores 97.9 and cli scores 93.7. This page calls that a narrow lead for nanobot.

Related comparisons