A fancy self-hosted monitoring tool
Scores
The two headline scores, measured daily, with 30, 90, and 180 day views.
Jul 19, 2026
Current35
Previous36
Weekly average
Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.
180 observed daily rows. Missing days are not fabricated.
40% Hot today + 40% Hot this week + 20% Breakout.
Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.
| Date | Stars | Stars 1d | Stars 7d | Stars 14d | Stars 30d | Stars 90d | Same-day multiplier | Weekly multiplier | Fortnight multiplier | Hot today | Hot week | Breakout | Stored score |
|---|
Jul 19, 2026
Current74
Previous73
Weekly average
Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.
180 observed daily rows. Missing days are not fabricated.
30% Continuity + 30% Closure + 20% Shipping + 10% Liveness + 10% Support burden.
Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.
Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.
| Date | Issues opened | Issues closed | PRs opened | PRs merged | Releases | Stars | Open issues | Pushed days ago | Continuity | Closure | Shipping | Liveness | Support burden | License | Observed days | Missing days | Needs healing | Stored score |
|---|
Reliability breakdown
Component scores measured daily from GitHub activity (2026-07-18).
Activity on 87 of 90 tracked days in the last 90 and 28 of 30 in the last 30.
Merged 73 of 171 PRs opened and closed 104 of 121 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
11 releases in the last 180 days, 4 in the last 90 and 0 in the last 30 — a steady cadence scores highest.
Last push 0 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
687 open issues against 89,308 stars — about 8 open issues per 1,000 stars. Lighter backlogs score higher.
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Topics
Jump into the topic listings this repository belongs to.
Measured history
Weekly GitHub totals with 30, 90, and 180 day views.
Jul 19, 2026
Current244
Previous306
Weekly star gains
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jul 19, 2026
Current89,269
Previous89,025
Cumulative total
Running total of the GitHub GraphQL stargazer count over time (not weekly deltas), reconstructed from starredAt events and totalCount in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jul 12, 2026
Current7
Previous10
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jul 12, 2026
Current9
Previous8
Weekly total
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jul 12, 2026
Current7
Previous13
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jul 12, 2026
Current6
Previous8
Weekly total
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jul 12, 2026
Current2
Previous3
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
178 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jul 16, 2026
Current0.50
Previous0.50
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is issues closed that day ÷ issues opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more issues than arrived that day.
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
137 observed daily rows. Missing days are not fabricated.
Per-day formula: issues closed that day ÷ issues opened that day; blank when nothing was opened (a gap, not a zero).
| Date | Issues opened | Issues closed | Stored score |
|---|
Jul 17, 2026
Current1.50
Previous1.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is pull requests closed that day ÷ pull requests opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more pull requests than arrived that day.
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
146 observed daily rows. Missing days are not fabricated.
Per-day formula: pull requests closed that day ÷ pull requests opened that day; blank when nothing was opened (a gap, not a zero).
| Date | PRs opened | PRs closed | Stored score |
|---|
Jul 19, 2026
Current0
Previous0
Weekly total
GitHub release published_at events bucketed by UTC day; drafts are excluded.
180 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
uptime-kuma is a self hosted monitoring application for tracking service availability and response status. The repository provides checks for websites and network endpoints, status pages, notifications, and historical uptime views. It is commonly used by operators, homelab users, and small teams monitoring APIs, websites, and internal services from their own infrastructure.
Join the conversation
Share what you know about uptime-kuma — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting uptime-kuma.
Project Q&A
Browse implementation threads tied directly to louislam/uptime-kuma. Each question links through to the full answer page.
Be the first to ask how teams run uptime-kuma in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses uptime-kuma — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post