A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 4.7 · narrow
A · leads
97.9
50,147 stars · MIT
B
93.2
24,177 stars · MIT
nanobot versus semantic-release is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. nanobot is written mainly in Python; semantic-release is written mainly in JavaScript. The composite score is 97.9 for nanobot and 93.2 for semantic-release.
nanobot has 50,147 GitHub stars to semantic-release's 24,177, a gap of 25,970 (2.07×). Forks are 8,755 for nanobot and 1,807 for semantic-release. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 83.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and semantic-release was last pushed on 17 November 2026 (0 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 410 for semantic-release (0.017 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both nanobot and semantic-release 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 nanobot (50,147 stars) and semantic-release (24,177 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: nanobot is open source, semantic-release is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 17 points (100 vs 83), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against semantic-release at 93.2, a 4.7 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 | nanobot | semantic-release |
|---|---|---|
| GitHub stars | 50,147 | 24,177 |
| Forks | 8,755 | 1,807 |
| Open issues | 872 | 410 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 93.2 |
Your lightweight open-source personal agent.
📦🚀 Fully automated version management and package publishing
nanobot has more GitHub stars: 50,147 versus 24,177 for semantic-release. The gap is 25,970 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and semantic-release as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. semantic-release 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 semantic-release scores 93.2. This page calls that a narrow lead for nanobot.