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.

Phantomape/ginger

https://github.com/Phantomape/ginger · scanned 2026-06-15 23:49 UTC (2 months, 3 weeks ago)

813 raw signals (0 security + 813 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 793 actionable findings from 1 signal source. 20 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 · 793 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 16 Low 749 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 793 Crowd 0 Layer: Software 27 Security 7 Data 1 Network 1 Frontend 1 Cicd 1 Quality 747 Api 8

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 2 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.

2 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 6 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.

6 matching findings on this repo

low Old/deprecated-named symbol `current_state_legacy` in scripts/build_alpha_memor…
low Old/deprecated-named symbol `test_backtester_emits_sharpe_daily_alongside_legac…
low Old/deprecated-named symbol `sharpe_legacy` in quant/backtester.py:3720
low Old/deprecated-named symbol `sleeve_health_report_v1` in quant/experiments/exp_…
low Old/deprecated-named symbol `cross_asset_risk_off_v2` in quant/experiments/lega…
low Old/deprecated-named symbol `static_macro_v1` in quant/experiments/legacy/exp_2…

View all legacy markers findings →

Commented-out code 21 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 (5 lines) in quant/filter.py:77
info Commented-code block (5 lines) in quant/test_volume_breadth_breakout_paper_slee…
info Commented-code block (112 lines) in quant/constants.py:108
info Commented-code block (6 lines) in quant/run_pipeline.py:413
info Commented-code block (7 lines) in quant/fill_model.py:21
info Commented-code block (6 lines) in quant/performance_engine.py:113
info Commented-code block (5 lines) in quant/signal_engine.py:142
info Commented-code block (9 lines) in quant/test_quant.py:3907
info Commented-code block (11 lines) in quant/backtester.py:1440
info Commented-code block (9 lines) in quant/portfolio_engine.py:98
info Commented-code block (5 lines) in quant/position_manager.py:193
info Commented-code block (6 lines) in quant/feature_layer.py:240

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/d85a2bd8-3c12-48da-8ac3-7ded37eecf9c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d85a2bd8-3c12-48da-8ac3-7ded37eecf9c/

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.