Repo brief: louislam/uptime-kuma

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T15:01:00.175Z · commit 013c381fc2a9

Verdict

Healthy — Healthy across all four use cases

• Last commit today
• 58+ active contributors
• Distributed ownership (top contributor 22% of recent commits)
• MIT licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Uptime Kuma is a self-hosted, Vue 3 + Node.js monitoring tool that tracks uptime across HTTP(s), TCP, DNS, WebSocket, Ping, Docker containers, and 90+ other services, with real-time dashboards, certificate tracking, and multi-channel notifications (Telegram, Discord, Slack, Email, etc.). It solves the problem of centralized, privacy-respecting infrastructure monitoring without recurring SaaS fees. Monolithic Vue + Node.js structure: frontend Vue components in src/components/ (organized by feature: notifications/, monitor settings, dialogs), backend likely in a sibling src/ directory, with Docker support (Dockerfile present), multi-language support via src/lang, and styling via SCSS…

Start here

Open these first:

• src/App.vue — Root Vue application component that sets up the main application layout and routing structure.
• src/components/MonitorSettingDialog.vue — Core UI component for configuring monitoring targets; used across the application for monitor creation and editing.
• src/components/NotificationDialog.vue — Manages all notification channel configuration; critical to alert delivery architecture.
• src/components/MonitorList.vue — Primary dashboard component displaying all monitors and their statuses; entry point for most user workflows.
• src/components/notifications — Directory containing 60+ notification provider integrations; each provider is independently maintainable and extensible.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/louislam/uptime-kuma.git
cd uptime-kuma
npm install
npm run dev

Note: Repository manifest not provided in data; verify package.json scripts before running. Docker Compose is documented as an alternative: docker compose up -d after pulling compose.yaml.

Daily commands:

No dev server command visible in provided data. Infer: npm run dev (typical Vue dev). Docker path: docker compose up -d or docker run -d -p 3001:3001 -v uptime-kuma:/app/data louislam/uptime-kuma:2. Verify scripts…

…shortened for this brief.

Key cautions & unknowns

• 1. File system constraint: NFS (Network File System) explicitly NOT supported per README; must use local volumes or bind mounts for data persistence. 2. Data volume path: /app/data is hardcoded in Docker examples;…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.