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.

koala73/worldmonitor

https://github.com/koala73/worldmonitor · scanned 2026-07-23 19:36 UTC (4 days, 18 hours ago)

245 raw signals (0 security + 245 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 18 hours ago · v9 · last Δ +3.2 (diff) · 241 actionable findings from 1 signal source. 4 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 · 241 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 29 Medium 50 Low 150 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 241 Crowd 0 Layer: Software 11 Frontend 32 Security 69 Network 3 Hardware 2 Cicd 3 Quality 103 Dependencies 16 Api 2

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 4 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.

4 matching findings on this repo

low Old/deprecated-named symbol `RefreshDataLegacy` in api/oauth/token.ts:290
low Old/deprecated-named symbol `passesLegacy` in scripts/notification-relay.cjs:884
low Old/deprecated-named symbol `scoreEnergyLegacy` in server/worldmonitor/resilien…
low Old/deprecated-named symbol `unstable_legacy` in public/pro/assets/index-kuCMAt…

View all legacy markers findings →

Commented-out code 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (12 lines) in src/main.ts:574 src/main.ts:574

View all commented-out code findings →

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

8 matching findings on this repo

medium Insecure pattern 'cors_wildcard' in vite.config.ts:745 vite.config.ts:745
low Very large file: vite.config.ts (1663 lines)
low Very large file: tests/deploy-config.test.mjs (2749 lines)
low Very large file: src/config/geo-map.ts (2745 lines)
low Very large file: src/config/feeds.ts (1211 lines)
low Very large file: src/config/panels.ts (1521 lines)
low Very large file: src/config/ai-datacenters.ts (3981 lines)
low Very large file: src/config/apt-groups.ts (1933 lines)

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/1d8c44e9-ff4a-4e26-92b1-a7c0dd8d2345/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1d8c44e9-ff4a-4e26-92b1-a7c0dd8d2345/

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.