A
semantic-release
95.9
24,177 stars · MIT
Workflow Automation
sim leads by 2.0 · narrow
A
95.9
24,177 stars · MIT
B · leads
97.9
30,151 stars · Apache-2.0
semantic-release versus sim is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. semantic-release is written mainly in JavaScript; sim is written mainly in TypeScript. The composite score is 95.9 for semantic-release and 97.9 for sim.
sim has 30,151 GitHub stars to semantic-release's 24,177, a gap of 5,974 (1.25×). Forks are 1,807 for semantic-release and 3,915 for sim. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 91 versus 100.
Push history: semantic-release was last pushed on 17 November 2026 (0 days ago), and sim was last pushed on 17 November 2026 (0 days ago). Open issues stand at 410 for semantic-release (0.017 per star) and 330 for sim (0.011 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. sim 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 semantic-release and 96 for sim. This is a procurement signal, not legal advice.
In Workflow Automation, both semantic-release (24,177 stars) and sim (30,151 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: semantic-release is open source, sim is open source.
sim 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 9 points (91 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
sim finishes ahead at 97.9 against semantic-release at 95.9, a 2.0 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 | semantic-release | sim |
|---|---|---|
| GitHub stars | 24,177 | 30,151 |
| Forks | 1,807 | 3,915 |
| Open issues | 410 | 330 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.9 | 97.9 |
📦🚀 Fully automated version management and package publishing
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
sim has more GitHub stars: 30,151 versus 24,177 for semantic-release. The gap is 5,974 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both semantic-release and sim as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. sim 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.
sim scores 97.9 and semantic-release scores 95.9. This page calls that a narrow lead for sim.