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.
Sign up free Scan another repo
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

WatWowMap/ReactMap

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
Combined
65.2
/100
Security checks
59
99 findings
System graph
71
100.0% cov · 109 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Dangling fetch: POST https://api.telegram.org/bot${this.strategy.botToken}/sendMessage (server/src/services/TelegramClient.js:216)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#2
Dangling fetch: GET http://ip-api.com/json/${ip}?fields=66846719&lang=en (server/src/services/logUserAuth.js:55)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#3
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:19
#4
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:27
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:32
#6
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/locales.yml
#7
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml:16
#8
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml
#9
Dockerfile runs as root: Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
#10
Very low test-to-source ratio
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.