A
docker_practice
84.2
26,370 stars · license n/a
DevOps
semaphore leads by 6.2 · narrow
A
84.2
26,370 stars · license n/a
B · leads
90.4
14,420 stars · MIT
docker_practice 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 84.2 for docker_practice and 90.4 for semaphore.
docker_practice has 26,370 GitHub stars to semaphore's 14,420, a gap of 11,950 (1.83×). Forks are 5,769 for docker_practice and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 83.
Push history: docker_practice was last pushed on 11 November 2026 (6 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 0 for docker_practice (0.000 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 96 and 52; activity scores are 92 and 100.
docker_practice 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 docker_practice 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). docker_practice is not (26,370 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: docker_practice is unpriced in this catalog, semaphore is open source.
The lead is split. docker_practice is furthest ahead on issue health (96 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 90.4 against docker_practice at 84.2, a 6.2 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 | docker_practice | semaphore |
|---|---|---|
| GitHub stars | 26,370 | 14,420 |
| Forks | 5,769 | 1,353 |
| Open issues | 0 | 1,075 |
| Adoption | 100 | 94 |
| Activity | 92 | 100 |
| Community | 100 | 83 |
| Issue health | 96 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 84.2 | 90.4 |
最新Docker容器技术,从真实案例中学习最佳实践!| Learn and understand Docker&Container technologies, with real DevOps practice!
Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.
docker_practice has more GitHub stars: 26,370 versus 14,420 for semaphore. The gap is 11,950 stars.
semaphore was pushed more recently: 17 November 2026 versus 11 November 2026 for docker_practice. That is 6 days apart.
Only semaphore is marked self-hostable. docker_practice is not.
docker_practice 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 90.4 and docker_practice scores 84.2. This page calls that a narrow lead for semaphore.