A
git-sim
75.6
4,695 stars · GPL-2.0
DevOps
Prometheus leads by 22.3 · decisive
A
75.6
4,695 stars · GPL-2.0
B · leads
97.9
67,671 stars · Apache-2.0
git-sim versus Prometheus is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. git-sim is written mainly in Python; Prometheus is written mainly in Go. The composite score is 75.6 for git-sim and 97.9 for Prometheus.
Prometheus has 67,671 GitHub stars to git-sim's 4,695, a gap of 62,976 (14.41×). Forks are 127 for git-sim and 11,035 for Prometheus. On the log scale used inside this pair, adoption is 76 versus 100, and the fork community is 52 versus 100.
Push history: git-sim was last pushed on 12 October 2026 (35 days ago), and Prometheus was last pushed on 17 November 2026 (0 days ago). Open issues stand at 11 for git-sim (0.002 per star) and 1,106 for Prometheus (0.016 per star). Issue-health scores are 96 and 84; activity scores are 78 and 100.
git-sim is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Prometheus 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 64 for git-sim and 96 for Prometheus. This is a procurement signal, not legal advice.
In DevOps, both git-sim (4,695 stars) and Prometheus (67,671 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: git-sim is open source, Prometheus is open source.
The lead is split. git-sim is furthest ahead on issue health (96 to 84), while Prometheus is furthest ahead on fork community (100 to 52). Choose the dimension a rollout cannot compromise on.
Prometheus finishes ahead at 97.9 against git-sim at 75.6, a 22.3 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 | git-sim | Prometheus |
|---|---|---|
| GitHub stars | 4,695 | 67,671 |
| Forks | 127 | 11,035 |
| Open issues | 11 | 1,106 |
| Adoption | 76 | 100 |
| Activity | 78 | 100 |
| Community | 52 | 100 |
| Issue health | 96 | 84 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 75.6 | 97.9 |
The visual layer for Git in your own repos: simulate, record, replay, audit, and share entire Git workflows, wherever you or your agents run them.
Prometheus is the CNCF metrics system: pull-based scraping, a time-series database, and PromQL. It is the usual baseline for Kubernetes monitoring.
Prometheus has more GitHub stars: 67,671 versus 4,695 for git-sim. The gap is 62,976 stars.
Prometheus was pushed more recently: 17 November 2026 versus 12 October 2026 for git-sim. That is 35 days apart.
Yes. This catalog marks both git-sim and Prometheus as self-hostable. Confirm each project's deploy docs before you plan a migration.
git-sim is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Prometheus 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.
Prometheus scores 97.9 and git-sim scores 75.6. This page calls that a decisive lead for Prometheus.