A
goreplay
65.7
19,326 stars · license n/a
DevOps
semaphore leads by 28.0 · decisive
A
65.7
19,326 stars · license n/a
B · leads
93.7
14,420 stars · MIT
goreplay versus semaphore is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 65.7 for goreplay and 93.7 for semaphore.
goreplay has 19,326 GitHub stars to semaphore's 14,420, a gap of 4,906 (1.34×). Forks are 102 for goreplay and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 64 versus 100.
Push history: goreplay was last pushed on 27 January 2026 (294 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 341 for goreplay (0.018 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 84 and 52; activity scores are 36 and 100.
goreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. semaphore 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 30 for goreplay and 96 for semaphore. This is a procurement signal, not legal advice.
Only semaphore is marked self-hostable here (14,420 stars, deploy score 100). goreplay is not (19,326 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: goreplay is unpriced in this catalog, semaphore is open source.
The lead is split. goreplay is furthest ahead on issue health (84 to 52), while semaphore is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
semaphore finishes ahead at 93.7 against goreplay at 65.7, a 28.0 point decisive 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 | goreplay | semaphore |
|---|---|---|
| GitHub stars | 19,326 | 14,420 |
| Forks | 102 | 1,353 |
| Open issues | 341 | 1,075 |
| Adoption | 100 | 97 |
| Activity | 36 | 100 |
| Community | 64 | 100 |
| Issue health | 84 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 65.7 | 93.7 |
GoReplay is an open-source tool for capturing and replaying live HTTP traffic into a test environment in order to continuously test your system with real data. It can be used to increase confidence in code deployments, configuration changes and infrastructure changes.
Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.
goreplay has more GitHub stars: 19,326 versus 14,420 for semaphore. The gap is 4,906 stars.
semaphore was pushed more recently: 17 November 2026 versus 27 January 2026 for goreplay. That is 294 days apart.
Only semaphore is marked self-hostable. goreplay is not.
goreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. semaphore 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.
semaphore scores 93.7 and goreplay scores 65.7. This page calls that a decisive lead for semaphore.