pickfit

BrowseInfra & DevOps tools

Uptime Kuma

Self-hosted monitoring tool that checks uptime of HTTP, TCP, ping, DNS and other services and sends notifications.

Use it

Before you install: known vulnerabilities

pickfit found 48 known high or critical vulnerabilities (58 findings, one per affected package version) in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • npm:mysql2 2.3.3 MySQL2 for Node Arbitrary Code Injection (GHSA-4rch-2fh8-94vw, critical, fixed in 3.9.7)
  • npm:protobufjs 7.2.6 protobufjs has an arbitrary code execution issue (GHSA-xq3m-2v4x-88gg, critical, fixed in 7.5.5)
See 8 more

48 more findings not listed here.

Linux x86_64

You need first

  • Runtimes: node>=20.4
  • System packages: git

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. git clone the repo

    git clone https://github.com/louislam/uptime-kuma.git && cd uptime-kuma
  2. npm run setup (checks out 2.5.11, npm ci --omit dev, downloads prebuilt dist)

    cd uptime-kuma && npm run setup
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

git clone https://github.com/louislam/uptime-kuma.git && cd uptime-kuma
cd uptime-kuma && npm run setup
curl -sS -X POST -H 'Content-Type: application/json' -d '{"dbConfig":{"type":"sqlite"}}' http://127.0.0.1:3001/setup-database && sleep 15 && curl -sS http://127.0.0.1:3001/api/entry-page
cd /home/sbx/work/uptime-kuma && node server/server.js --data-dir=/tmp/kuma-data
curl -sS -X POST -H 'Content-Type: application/json' -d '{"dbConfig":{"type":"sqlite"}}' http://127.0.0.1:3001/setup-database && sleep 15 && curl -sS http://127.0.0.1:3001/api/entry-page

Check that it works

curl -sS -X POST -H 'Content-Type: application/json' -d '{"dbConfig":{"type":"sqlite"}}' http://127.0.0.1:3001/setup-database && sleep 15 && curl -sS http://127.0.0.1:3001/api/entry-page

The output should contain “{"ok":true}”.

First thing to try

cd "$HOME"/work/uptime-kuma && node server/server.js --data-dir=/tmp/kuma-data
curl -sS -X POST -H 'Content-Type: application/json' -d '{"dbConfig":{"type":"sqlite"}}' http://127.0.0.1:3001/setup-database && sleep 15 && curl -sS http://127.0.0.1:3001/api/entry-page

Open http://127.0.0.1:3001 in a web browser; the first screen asks you to set up the database and create an admin account.

What it does

  • Monitor uptime of HTTP, TCP, ping, DNS and Docker
    Not tested
  • Send notifications to more than 90 services
    Not tested
  • Host multiple status pages
    Not tested
  • Show certificate information
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • monitor uptime of HTTP(s) websites and TCP services
  • publish status pages on custom domains
  • get downtime alerts via Telegram, Discord or email

An alternative to Uptime Robot and statping.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version 2.5.11

Differences the test machine hit

  • README: npm run setup, then node server/server.js; Uptime Kuma is now running on http://localhost:3001
    In the test: In v2, a first run waits on a database-setup step; with no browser, POST {"dbConfig":{"type":"sqlite"}} to /setup-database first, then create the admin account through the socket.io 'setup' event
  • README: (no mention of an API)
    In the test: Uptime Kuma has no REST API for monitors. A headless socket.io client hung until it sent an Origin header that matches the server URL; no connect_error was printed
  • README: git clone (master)
    In the test: npm run setup checks out the pinned release tag 2.5.11 and downloads a prebuilt dist.tar.gz from GitHub releases (a binary archive, not read)

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.