A
edict
84.0
17,077 stars · MIT
Workflow Automation
nanobot leads by 13.9 · clear
A
84.0
17,077 stars · MIT
B · leads
97.9
50,147 stars · MIT
edict versus nanobot is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 84.0 for edict and 97.9 for nanobot.
nanobot has 50,147 GitHub stars to edict's 17,077, a gap of 33,070 (2.94×). Forks are 1,771 for edict and 8,755 for nanobot. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 82 versus 100.
Push history: edict was last pushed on 28 September 2026 (50 days ago), and nanobot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 15 for edict (0.001 per star) and 872 for nanobot (0.017 per star). Issue-health scores are 96 and 84; activity scores are 58 and 100.
Both edict and nanobot 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 edict (17,077 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: edict is open source, nanobot is open source.
The lead is split. edict is furthest ahead on issue health (96 to 84), while nanobot is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
nanobot finishes ahead at 97.9 against edict at 84.0, a 13.9 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 | edict | nanobot |
|---|---|---|
| GitHub stars | 17,077 | 50,147 |
| Forks | 1,771 | 8,755 |
| Open issues | 15 | 872 |
| Adoption | 90 | 100 |
| Activity | 58 | 100 |
| Community | 82 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.0 | 97.9 |
🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails
Your lightweight open-source personal agent.
nanobot has more GitHub stars: 50,147 versus 17,077 for edict. The gap is 33,070 stars.
nanobot was pushed more recently: 17 November 2026 versus 28 September 2026 for edict. That is 50 days apart.
Yes. This catalog marks both edict and nanobot as self-hostable. Confirm each project's deploy docs before you plan a migration.
edict 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. 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.
nanobot scores 97.9 and edict scores 84.0. This page calls that a clear lead for nanobot.