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
90 of your 216 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 7.09s · analysis 18.07s · 14.7 MB · GitHub API rate-limit (preflight)

sansan0/TrendRadar

https://github.com/sansan0/TrendRadar · scanned 2026-06-05 09:52 UTC (5 days, 17 hours ago) · 10 languages

388 raw signals (206 security + 182 graph) 34th percentile · Python · medium (20-100K LoC) System graph score 60 (lower by 17)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 17 hours ago · v2 · 169 actionable findings from 2 signal sources. 127 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
55.8
/100
Security checks
51
109 findings
System graph
60
100.0% cov · 60 findings
Critical
6
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 35.2 0.25 8.80
testing_score 0.0 0.20 0.00
documentation_score 88.7 0.15 13.30
practices_score 59.0 0.15 8.85
code_quality 13.6 0.10 1.36
Overall 1.00 43.6
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 6 High 39 Medium 41 Low 60 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 109 System graph 60 Crowd 0 Layer: Quality 52 Software 82 Cicd 8 Security 9 Api 1 Frontend 3 Network 11 Hardware 3

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

#1
.env file present in repo: docker/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#2
Privileged port 20 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml
#3
Privileged port 11 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml
#4
Privileged port 13 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml
#5
Privileged port 15 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml
#6
Privileged port 17 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml
#7
Privileged port 19 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml
#8
Privileged port 23 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml
#9
Privileged port 21 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml
#10
Privileged port 12 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in config/timeline.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
config/timeline.yaml

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/1178e500-7bf6-4ce8-86a4-9303c4049b1d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1178e500-7bf6-4ce8-86a4-9303c4049b1d/

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.