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.

deepsearchaiapp/worldmonitor

https://github.com/deepsearchaiapp/worldmonitor · scanned 2026-06-17 01:55 UTC (1 month, 1 week ago)

403 raw signals (0 security + 403 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -21.9 (diff) · 401 actionable findings from 1 signal source. 2 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 · 401 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 117 Medium 132 Low 105 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 401 Crowd 0 Layer: Frontend 74 Hardware 3 Security 61 Cicd 4 Quality 135 Api 124

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 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `unstable_legacy` in public/pro/assets/index-CIvSGt…

View all legacy markers findings →

Commented-out code 44 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 (5 lines) in tests/edge-functions.test.mjs:132
info Commented-code block (5 lines) in api/bootstrap.js:84
info Commented-code block (5 lines) in api/youtube/embed.js:96
info Commented-code block (7 lines) in api/live-news/v6/list-us-headlines.ts:78
info Commented-code block (6 lines) in api/world-brief/v1/weekly-digest.ts:90
info Commented-code block (7 lines) in api/ops/_probe-core.js:158
info Commented-code block (6 lines) in api/intel-news/v1/enrich.ts:31
info Commented-code block (5 lines) in api/intel-news/v1/refresh.ts:301
info Commented-code block (8 lines) in scripts/ais-relay.cjs:301
info Commented-code block (7 lines) in src/utils/circuit-breaker.ts:216
info Commented-code block (5 lines) in src/components/Map.ts:3601
info Commented-code block (6 lines) in src/components/LiveNewsPanel.ts:1285

View all commented-out code findings →

Config drift 15 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:851
low Stray `console.log` in TS/JS — src/config/feeds.ts:1332
medium Insecure pattern 'cors_wildcard' in vite.config.ts:499 vite.config.ts:499
medium Insecure pattern 'direct_innerhtml_assignment' in src/components/RuntimeConfigP… src/components/RuntimeConfigPanel.ts:212
low Very large file: src/config/feeds.ts (1349 lines)
low Very large file: src/config/geo.ts (3259 lines)
low Very large file: src/config/ai-datacenters.ts (3981 lines)
medium `fetch()` without try/.catch or AbortSignal — vite.config.ts:485
medium `fetch()` without try/.catch or AbortSignal — src/services/runtime-config.ts:523
info Commented-code block (5 lines) in src/config/index.ts:1
info Commented-code block (5 lines) in src/config/panels.ts:8
info Commented-code block (5 lines) in src/config/feeds.ts:8

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/42b5acf1-c6fd-49ab-9495-e6efcced01b6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/42b5acf1-c6fd-49ab-9495-e6efcced01b6/

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.