louislam/uptime-kuma

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

34 of your 205 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.54s · analysis 22.87s · 8.0 MB · GitHub API rate-limit (preflight)

https://github.com/louislam/uptime-kuma · scanned 2026-06-05 07:07 UTC (5 days, 23 hours ago) · 10 languages

526 raw signals (196 security + 330 graph) 39th percentile · Javascript · medium (20-100K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 23 hours ago · v2 · 288 actionable findings from 2 signal sources. 73 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 159 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	0.0	0.25	0.00
`testing_score`	42.0	0.20	8.40
`documentation_score`	82.7	0.15	12.40
`practices_score`	100.0	0.15	15.00
`code_quality`	57.6	0.10	5.76
Overall		1.00	54.3

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 7 High 55 Medium 56 Low 133 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 129 System graph 159 Crowd 0 Layer: Quality 51 Security 19 Software 114 Cicd 18 Frontend 39 Network 3 Hardware 3 Api 41

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 6 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

6 matching findings on this repo

info Commented-code block (5 lines) in server/server.js:1481
info Commented-code block (5 lines) in server/monitor-types/snmp.js:25
info Commented-code block (5 lines) in server/modules/apicache/apicache.js:765
info Commented-code block (15 lines) in server/model/monitor.js:1433
info Commented-code block (5 lines) in db/knex_migrations/2026-01-06-0000-fix-domain…
info Commented-code block (5 lines) in src/icon.js:4

View all commented-out code findings →

Config drift 4 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

4 matching findings on this repo

high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… extra/healthcheck.go:27
low File has no detected symbols: ecosystem.config.js
low File has no detected symbols: config/vite.config.js
low File has no detected symbols: config/playwright.config.js

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/153ee255-4dcc-4e29-88db-07a1f48f9b4c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/153ee255-4dcc-4e29-88db-07a1f48f9b4c/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.