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

Scan timing: clone 13.53s · analysis 20.13s · 63.2 MB · GitHub API rate-limit (preflight)

ubugeeei-prod/vize

https://github.com/ubugeeei-prod/vize · scanned 2026-06-05 18:27 UTC (4 days, 19 hours ago) · 10 languages

476 raw signals (100 security + 376 graph) 11/13 scanners ran 92nd percentile · Rust · large (100-500K LoC)

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

Complete repo analysis

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

JSON
Combined
82.3
/100
Security checks
81
43 findings
System graph
83
100.0% cov · 186 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 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 76.0 0.20 15.20
documentation_score 96.0 0.15 14.40
practices_score 86.0 0.15 12.90
code_quality 70.0 0.10 7.00
Overall 1.00 83.5
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
Severity: Critical 0 High 4 Medium 14 Low 175 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 43 System graph 186 Crowd 0 Layer: Quality 57 Software 53 Security 3 Api 1 Frontend 109 Network 5 Cicd 1

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

#1
Privileged port 3 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .github/workflows/check.yml is a real port, change the binding to ≥1024 or run behind a proxy.
.github/workflows/check.yml
#2
Privileged port 11 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .github/workflows/check.yml is a real port, change the binding to ≥1024 or run behind a proxy.
.github/workflows/check.yml
#3
Privileged port 12 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .github/workflows/check.yml is a real port, change the binding to ≥1024 or run behind a proxy.
.github/workflows/check.yml
#4
Privileged port 2 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .github/workflows/e2e.yml is a real port, change the binding to ≥1024 or run behind a proxy.
.github/workflows/e2e.yml
#5
Privileged port 23 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .github/workflows/e2e.yml is a real port, change the binding to ≥1024 or run behind a proxy.
.github/workflows/e2e.yml
#6
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/tool-benchmark.yml
#7
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml
#8
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/deploy-docs.yml
#9
`fetch()` without try/.catch or AbortSignal — npm/vite-plugin-musea/gallery/api.ts:68
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in npm/vite-plugin-musea/gallery/api.ts:68, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#10
`fetch()` without try/.catch or AbortSignal — npm/vite-plugin-musea/src/gallery/index.ts:48
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in npm/vite-plugin-musea/src/gallery/index.ts:48, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

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/838df817-0857-4287-990d-e32b2463fcfc/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/838df817-0857-4287-990d-e32b2463fcfc/

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.