issue-statusvsprometheus
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| issue-status | prometheus | |
|---|---|---|
| Score | 47/100 | 90/100 |
| Rank in category | #31 of 51 in Monitoring & observability | #1 of 104 in Monitoring & observability |
| GitHub stars | 429 | 66 828 |
| Stars, last 30 days | — | +632 |
| Stable releases, 12 months | 0 | 16 |
| Latest release | — | v3.15.1 · 21 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | No | Yes |
| License | MIT | Apache-2.0 |
| Main language | Typescript | Go |
Which one should you pick?
prometheus scores 90/100 against 47/100 for issue-status, so it is the safer default.
prometheus ships more often: 16 stable releases in the past year, against 0 for issue-status.
If you want the quickest setup, issue-status is easier to run; prometheus needs more configuration.
prometheus is growing faster right now (+632 stars in 30 days).
issue-status details →prometheus details →
Swap a project
Keep issue-status, compare it with
Keep prometheus, compare it with