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.
5 of your 10 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 47.8s for a 63.8 MB repo slow.
  • Repobility's analysis ran in 0.11s after the clone landed.

Misaka-blog/chromego_merge

https://github.com/Misaka-blog/chromego_merge · scanned 2026-06-05 15:07 UTC (5 days, 2 hours ago) · 10 languages

73 raw signals (9 security + 64 graph) 11/13 scanners ran 83rd percentile · Python · tiny (<2K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 55.0 0.15 8.25
security_score 100.0 0.25 25.00
testing_score 70.0 0.20 14.00
documentation_score 60.0 0.15 9.00
practices_score 72.0 0.15 10.80
code_quality 69.0 0.10 6.90
Overall 1.00 74.0
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

#1
Privileged port 180 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#2
Privileged port 81 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#3
Privileged port 82 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#4
Privileged port 83 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#5
Privileged port 84 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#6
Privileged port 85 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#7
Privileged port 86 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#8
Privileged port 87 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#9
Privileged port 88 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.yaml
#10
Privileged port 89 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in sub/merged_proxies_new.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
sub/merged_proxies_new.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/8af2125d-6eee-404c-90f0-1c9ed2519c73/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8af2125d-6eee-404c-90f0-1c9ed2519c73/

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.