WatWowMap/ReactMap

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.

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

Scan timing: clone 3.62s · analysis 43.99s · 7.2 MB · GitHub preflight 556ms

https://github.com/WatWowMap/ReactMap · scanned 2026-06-05 17:19 UTC (4 days, 22 hours ago) · 10 languages

398 raw signals (142 security + 256 graph) 35th percentile · Javascript · medium (20-100K LoC) System graph score 71 (lower by 17)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 22 hours ago · v2 · 208 actionable findings from 2 signal sources. 62 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 · 109 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	38.7	0.25	9.68
`testing_score`	0.0	0.20	0.00
`documentation_score`	78.6	0.15	11.79
`practices_score`	80.0	0.15	12.00
`code_quality`	76.8	0.10	7.68
Overall		1.00	53.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 40 Medium 33 Low 102 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 99 System graph 109 Crowd 0 Layer: Quality 40 Security 29 Software 90 Cicd 9 Frontend 15 Hardware 3 Api 22

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 `getLegacy` in server/src/models/Pokemon.js:711
low Old/deprecated-named symbol `onlyLegacy` in server/src/graphql/resolvers.js:270
low Old/deprecated-named symbol `onlyLegacy` in server/src/filters/pokemon/Backend.…
low Old/deprecated-named symbol `onlyLegacy` in src/pages/map/components/QueryData.…

View all legacy markers findings →

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

4 matching findings on this repo

info Commented-code block (11 lines) in ecosystem.config.example.js:17
info Commented-code block (10 lines) in server/src/graphql/resolvers.js:388
info Commented-code block (19 lines) in src/services/Assets.js:7
info Commented-code block (14 lines) in src/features/webhooks/human/area/AreaGroup.j…

View all commented-out code findings →

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

7 matching findings on this repo

low File has no detected symbols: ecosystem.config.example.js
low File has no detected symbols: packages/types/lib/config.d.ts
low File has no detected symbols: packages/config/lib/index.d.ts
low File has no detected symbols: packages/config/lib/scripts/configCheck.js
low File has no detected symbols: server/src/routes/api/v1/config.js
low Stray `console.log` in TS/JS — packages/config/lib/scripts/genEnvConfig.js:42
info Commented-code block (11 lines) in ecosystem.config.example.js:17

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/0947bacf-8128-451a-abff-7f1f2911cf41/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0947bacf-8128-451a-abff-7f1f2911cf41/

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.