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.

corgiolu-labs/jonny5

https://github.com/corgiolu-labs/jonny5 · scanned 2026-06-17 01:51 UTC (1 month, 1 week ago)

91 raw signals (0 security + 91 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

66.7% cov · 77 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 29 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 77 Crowd 0 Layer: Software 11 Frontend 3 Security 23 Cicd 1 Quality 39

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 3 findings

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.

3 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 5 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

5 matching findings on this repo

low Old/deprecated-named symbol `rx_legacy` in raspberry/controller/spi_dataplane/j…
low Old/deprecated-named symbol `mirror_legacy` in raspberry/controller/web_service…
low Old/deprecated-named symbol `mirror_legacy` in raspberry/controller/web_service…
low Old/deprecated-named symbol `mirror_legacy` in raspberry/controller/web_service…
low Old/deprecated-named symbol `mirror_legacy` in raspberry/controller/web_service…

View all legacy markers findings →

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

12 matching findings on this repo

info Commented-code block (6 lines) in raspberry/controller/spi_dataplane/j5vr_spi_b…
info Commented-code block (7 lines) in raspberry/controller/spi_dataplane/j5vr_frame…
info Commented-code block (7 lines) in raspberry/controller/web_services/runtime_con…
info Commented-code block (5 lines) in raspberry/controller/web_services/settings_ma…
info Commented-code block (5 lines) in raspberry/controller/web_services/ws_handlers…
info Commented-code block (10 lines) in raspberry/controller/web_services/head_assis…
info Commented-code block (5 lines) in raspberry/controller/web_services/ws_server.p…
info Commented-code block (7 lines) in raspberry/controller/teleop/__init__.py:1
info Commented-code block (6 lines) in web/dashboard/js/controllers.js:76
info Commented-code block (5 lines) in web/dashboard/js/dashboard.js:135
info Commented-code block (5 lines) in web/dashboard/js/vr-live.js:51
info Commented-code block (7 lines) in web/dashboard/js/imu_vr.js:96

View all commented-out code findings →

Config drift 2 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

2 matching findings on this repo

low Old/deprecated-named symbol `mirror_legacy` in raspberry/controller/web_service…
info Commented-code block (7 lines) in raspberry/controller/web_services/runtime_con…

View all config drift 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/ab89d68d-b28e-41a8-a8f8-18bfc5395483/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ab89d68d-b28e-41a8-a8f8-18bfc5395483/

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.