A · leads
semantic-release
97.5
24,177 stars · MIT
Workflow Automation
semantic-release leads by 5.0 · narrow
A · leads
97.5
24,177 stars · MIT
B
92.5
23,434 stars · AGPL-3.0
semantic-release versus skyvern 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; skyvern is written mainly in Python. The composite score is 97.5 for semantic-release and 92.5 for skyvern.
semantic-release has 24,177 GitHub stars to skyvern's 23,434, a gap of 743 (1.03×). Forks are 1,807 for semantic-release and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 97 versus 100.
Push history: semantic-release was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 410 for semantic-release (0.017 per star) and 301 for skyvern (0.013 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for semantic-release and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both semantic-release (24,177 stars) and skyvern (23,434 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, skyvern is open source.
The lead is split. semantic-release is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on fork community (100 to 97). Choose the dimension a rollout cannot compromise on.
semantic-release finishes ahead at 97.5 against skyvern at 92.5, a 5.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 | skyvern |
|---|---|---|
| GitHub stars | 24,177 | 23,434 |
| Forks | 1,807 | 2,246 |
| Open issues | 410 | 301 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.5 | 92.5 |
📦🚀 Fully automated version management and package publishing
Automate browser based workflows with AI
semantic-release has more GitHub stars: 24,177 versus 23,434 for skyvern. The gap is 743 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both semantic-release and skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
semantic-release scores 97.5 and skyvern scores 92.5. This page calls that a narrow lead for semantic-release.