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.

absrzvi/vison

https://github.com/absrzvi/vison · scanned 2026-06-17 01:28 UTC (1 month, 2 weeks ago)

82 raw signals (0 security + 82 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -22.2 (diff) · 71 actionable findings from 1 signal source. 11 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 71 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 17 Medium 27 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 71 Crowd 0 Layer: Software 7 Frontend 4 Network 3 Hardware 8 Security 19 Quality 30

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.

Duplicates & near-duplicates 1 finding

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Commented-out code 9 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/`.

9 matching findings on this repo

info Commented-code block (6 lines) in inference/src/inference/pipeline.py:34
info Commented-code block (5 lines) in inference/src/inference/zone_counter.py:175
info Commented-code block (6 lines) in claude-design-mockups/ui_kits/railnet_passeng…
info Commented-code block (6 lines) in cloud-sync/tests/integration/test_ordered_flu…
info Commented-code block (5 lines) in cloud-sync/src/cloud_sync/main.py:70
info Commented-code block (6 lines) in event-store/tests/integration/test_event_stor…
info Commented-code block (5 lines) in shared/src/oebb_shared/events/payloads.py:382
info Commented-code block (5 lines) in fusion/tests/unit/test_health.py:395
info Commented-code block (7 lines) in fusion/src/fusion/health.py:303

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/e1d23794-10db-495c-98a7-260d636e4e33/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e1d23794-10db-495c-98a7-260d636e4e33/

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.