koala73/worldmonitor

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.

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

Scan timing: clone 22.72s · analysis 24.76s · 61.7 MB · GitHub API rate-limit (preflight)

https://github.com/koala73/worldmonitor · scanned 2026-06-05 10:24 UTC (5 days, 15 hours ago) · 10 languages

1473 raw signals (155 security + 1318 graph) 11/13 scanners ran 73rd percentile · Typescript · large (100-500K LoC) System graph score 68 (higher by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 15 hours ago · v2 · 710 actionable findings from 2 signal sources. 104 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 · 656 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	36.0	0.20	7.20
`documentation_score`	100.0	0.15	15.00
`practices_score`	97.0	0.15	14.55
`code_quality`	67.0	0.10	6.70
Overall		1.00	81.2

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 79 Medium 135 Low 179 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 54 System graph 656 Crowd 0 Layer: Security 12 Cicd 17 Quality 479 Software 54 Frontend 65 Hardware 6 Api 77

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.

Legacy markers 3 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

3 matching findings on this repo

low Old/deprecated-named symbol `CodeDataLegacy` in api/oauth/token.ts:274
low Old/deprecated-named symbol `scoreEnergyLegacy` in server/worldmonitor/resilien…
low Old/deprecated-named symbol `unstable_legacy` in public/pro/assets/index-cpXKHx…

View all legacy markers findings →

Commented-out code 281 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/`.

12 matching findings on this repo

info Commented-code block (8 lines) in vite.config.ts:16
info Commented-code block (14 lines) in middleware.ts:15
info Commented-code block (7 lines) in api/symbol-search.ts:45
info Commented-code block (8 lines) in api/_sentry-common.js:119
info Commented-code block (8 lines) in api/user-prefs.ts:58
info Commented-code block (5 lines) in api/mcp-proxy.ts:12
info Commented-code block (8 lines) in api/widget-agent.ts:98
info Commented-code block (7 lines) in api/mcp.ts:24
info Commented-code block (6 lines) in api/_rate-limit.js:25
info Commented-code block (8 lines) in api/notification-channels.ts:294
info Commented-code block (7 lines) in api/latest-brief.ts:42
info Commented-code block (5 lines) in api/seed-contract-probe.ts:103

View all commented-out code findings →

Config drift 26 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.

12 matching findings on this repo

low File has no detected symbols: playwright.config.ts
low Stray `console.log` in TS/JS — vite.config.ts:1059
low Stray `console.log` in TS/JS — src/config/feeds.ts:1194
low Very large file: vite.config.ts (1411 lines)
low Very large file: src/config/geo.ts (3546 lines)
low Very large file: src/config/feeds.ts (1211 lines)
low Very large file: src/config/panels.ts (1388 lines)
low Very large file: src/config/ai-datacenters.ts (3981 lines)
low Very large file: src/config/apt-groups.ts (1933 lines)
info Commented-code block (8 lines) in vite.config.ts:16
medium `fetch()` without try/.catch or AbortSignal — vite.config.ts:619
info Commented-code block (5 lines) in convex/config/productCatalog.ts:254

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/c4e5290e-2554-4239-8548-581b533a4bae/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c4e5290e-2554-4239-8548-581b533a4bae/

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.