louislam/uptime-kuma
This is a comprehensive uptime monitoring and status page service that supports a wide variety of service checks, including HTTP, TCP, DNS, gRPC, and database protocols. It provides a Vue 3-based dashboard for configuring monitors, managing notifications across numerous providers, and publishing customizable status pages with real-time analytics. The system handles data retention, background maintenance, and progressive web app capabilities, all secured by robust authentication and rate limiting.
51.6
Adequate · 2 August 2026
59k
lines of production code
JavaScript
primary language
11
bus factor · 1,078 authors in all
3
measurements over time
How it got here
2021 · Vue 3 migration and server modularization
This period focused on modernizing the frontend by migrating to Vue 3 and restructuring the backend into modular, single-responsibility components. The team also expanded notification provider support, introduced PWA capabilities, and improved code organization through extensive refactoring and configuration centralization.
23 changes
2022–2024 · monitoring and release automation
This period focused on expanding the monitoring system to support a wide variety of new service types and database conditions, alongside significant database schema updates. The work also included adding authentication support, improving test coverage for new features, and automating the release process.
14 changes
2025–2026 · Analytics integration and test coverage expansion
This period focused on implementing multi-provider analytics support for status pages, allowing users to integrate with services like Google Analytics and Plausible. Concurrently, the codebase expanded its test coverage by adding manual tests for Redis TLS and gRPC, alongside comprehensive unit tests for backend monitors and notification providers.
5 changes
Survey your own repository
louislam/uptime-kuma was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 2 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit f766c38fa6 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.