wchl3927/vi-pro-pipeline

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.

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

https://github.com/wchl3927/vi-pro-pipeline.git · scanned 2026-05-28 23:09 UTC (1 week ago) · 10 languages

70 findings (34 legacy + 36 scanner) 1st percentile · Python · small (2-20K LoC) Scanner says 73 (lower by 33)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week ago · v2 · 52 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

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 29 Medium 6 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 34 9-layer 18 Crowd 0 Layer: Quality 37 Software 7 Api 1 Frontend 1 Security 2 Cicd 4

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 28 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

medium Bare except continues silently calculate_stocks.py:3464
medium Bare except continues silently calculate_stocks.py:670
medium Bare except continues silently calculate_stocks.py:5036
medium Bare except continues silently calculate_stocks.py:4783
medium Bare except continues silently calculate_stocks.py:4053
medium Bare except continues silently calculate_stocks.py:3999
medium Bare except continues silently calculate_stocks.py:3942
medium Bare except continues silently calculate_stocks.py:3535
medium Bare except continues silently calculate_crypto.py:2867
medium Bare except continues silently calculate_crypto.py:2695
medium Bare except continues silently calculate_crypto.py:3572
medium Bare except continues silently calculate_crypto.py:117

View all fragile runtime findings →

Commented-out code 2 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

2 matching findings on this repo

info Commented-code block (5 lines) in calculate_crypto.py:25
info Commented-code block (5 lines) in calculate_stocks.py:164

View all commented-out code findings →

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.