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.git · scanned 2026-07-23 05:58 UTC (5 days, 13 hours ago)

1444 raw signals (0 security + 1444 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 13 hours ago · v2 · 1440 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 · 1440 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 172 Medium 266 Low 190 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1440 Crowd 0 Layer: Software 11 Frontend 68 Security 130 Quality 1062 Network 3 Hardware 2 Cicd 3 Api 161

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

6 matching findings on this repo

low Old/deprecated-named symbol `user_pro_legacy` in tests/gateway-internal-mcp.tes…
low Old/deprecated-named symbol `RefreshDataLegacy` in api/oauth/token.ts:290
low Old/deprecated-named symbol `passesLegacy` in scripts/notification-relay.cjs:881
low Old/deprecated-named symbol `user_legacy` in server/__tests__/entitlement-check…
low Old/deprecated-named symbol `scoreEnergyLegacy` in server/worldmonitor/resilien…
low Old/deprecated-named symbol `unstable_legacy` in public/pro/assets/index-h3PD5r…

View all legacy markers findings →

Commented-out code 798 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 (7 lines) in vite.config.ts:28
info Commented-code block (23 lines) in middleware.ts:16
info Commented-code block (6 lines) in tests/fred-proxy-transient-classify.test.mjs:6
info Commented-code block (6 lines) in tests/brief-dedup-replay-log.test.mjs:116
info Commented-code block (8 lines) in tests/map-container-size-cache.test.mjs:10
info Commented-code block (5 lines) in tests/cloud-prefs-flush-version-guard.test.mj…
info Commented-code block (7 lines) in tests/relay-tanker-shipstatic.test.mjs:63
info Commented-code block (6 lines) in tests/lcp-attribution-contract.test.mjs:105
info Commented-code block (7 lines) in tests/feelgood-classifier.test.mjs:3
info Commented-code block (5 lines) in tests/mcp-output-budget.test.mjs:6
info Commented-code block (6 lines) in tests/seed-extra-key-leak-guard.test.mjs:3
info Commented-code block (6 lines) in tests/portwatch-retry-on-empty.test.mjs:3

View all commented-out code findings →

Config drift 35 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 Stray `console.log` in TS/JS — vite.config.ts:1311
low Stray `console.log` in TS/JS — src/config/feeds.ts:1194
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 (2644 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)
info Commented-code block (7 lines) in vite.config.ts:28
medium `fetch()` without try/.catch or AbortSignal — vite.config.ts:731

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/a67d0ef9-1c72-41e2-9f3b-4a3aaf8079ac/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a67d0ef9-1c72-41e2-9f3b-4a3aaf8079ac/

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.