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

Scan timing: clone 1.65s · analysis 0.45s · 0.5 MB · GitHub preflight 510ms

wchl3927/vi-pro-pipeline

https://github.com/wchl3927/vi-pro-pipeline.git · scanned 2026-05-28 23:09 UTC (2 weeks, 3 days ago) · 10 languages

70 raw signals (34 security + 36 graph) 1st percentile · Python · small (2-20K LoC) System graph score 73 (lower by 33)

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

Complete repo analysis

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

JSON
Combined
64.9
/100
Security checks
57
7 findings
System graph
73
77.8% cov · 14 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 30.0 0.15 4.50
security_score 100.0 0.25 25.00
testing_score 0.0 0.20 0.00
documentation_score 0.0 0.15 0.00
practices_score 55.0 0.15 8.25
code_quality 25.0 0.10 2.50
Overall 1.00 40.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 0 Medium 6 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 14 Crowd 0 Layer: Quality 13 Cicd 1 Software 3 Api 1 Frontend 1 Security 2

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

#1
Possible secret in calculate_crypto.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in calculate_crypto.py:13; move to env var / secrets manager.
calculate_crypto.py:13
#2
Possible secret in calculate_stocks.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in calculate_stocks.py:485; move to env var / secrets manager.
calculate_stocks.py:485
#3
Very low test-to-source ratio
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity
#4
Network/subprocess call without timeout or try/except — calculate_crypto.py:4737
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in calculate_crypto.py:4737 to prevent hung calls.
#5
Network/subprocess call without timeout or try/except — calculate_stocks.py:4997
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in calculate_stocks.py:4997 to prevent hung calls.
#6
Possibly dead Python function: fetch_price_history_binance
GapSeverity.LOW Layer.SOFTWARE score 0.140
Why: low severity · clean removal is a safe PR
Fix: If genuinely unused, remove the function in calculate_crypto.py:124; if framework-registered, add a docstring.
calculate_crypto.py:124
#7
Possibly dead Python function: fetch_coingecko_detail
GapSeverity.LOW Layer.SOFTWARE score 0.140
Why: low severity · clean removal is a safe PR
Fix: If genuinely unused, remove the function in calculate_crypto.py:315; if framework-registered, add a docstring.
calculate_crypto.py:315
#8
Possibly dead Python function: fetch_bitcoin_hashrate
GapSeverity.LOW Layer.SOFTWARE score 0.140
Why: low severity · clean removal is a safe PR
Fix: If genuinely unused, remove the function in calculate_crypto.py:510; if framework-registered, add a docstring.
calculate_crypto.py:510
#9
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.LOW Layer.CICD score 0.100
Why: low severity
.github/workflows/update_crypto.yml:15
#10
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.LOW Layer.CICD score 0.100
Why: low severity
.github/workflows/update_crypto.yml:22

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/f3913967-0d48-43d5-969a-96d35560314c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f3913967-0d48-43d5-969a-96d35560314c/

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.