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.

cipher813/alpha-engine-predictor

https://github.com/cipher813/alpha-engine-predictor · scanned 2026-06-17 01:49 UTC (1 month, 1 week ago)

97 raw signals (0 security + 97 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.7 (diff) · 89 actionable findings from 1 signal source. 8 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 89 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 4 Low 28 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 89 Crowd 0 Layer: Software 3 Hardware 2 Cicd 4 Quality 80

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 →

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 `no_git_sha_tag_legacy` in inference/deploy_drift.p…
low Old/deprecated-named symbol `test_wave3_reader_prefers_new_prefix_over_legacy` …
low Old/deprecated-named symbol `no_git_sha_tag_legacy` in tests/test_deploy_drift_…
low Old/deprecated-named symbol `test_load_prices_prefers_reference_prefix_over_leg…
low Old/deprecated-named symbol `test_bear_stretches_matches_legacy` in tests/test_…

View all legacy markers findings →

Commented-out code 56 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 config.py:47
info Commented-code block (12 lines) in training/model_zoo.py:236
info Commented-code block (5 lines) in training/meta_trainer.py:62
info Commented-code block (7 lines) in training/train_handler.py:65
info Commented-code block (5 lines) in training/risk_model_persist.py:60
info Commented-code block (8 lines) in training/leakfree_meta_ic.py:182
info Commented-code block (5 lines) in inference/deploy_drift.py:37
info Commented-code block (6 lines) in inference/daily_predict.py:49
info Commented-code block (5 lines) in inference/handler.py:50
info Commented-code block (6 lines) in inference/lib_pin_drift.py:55
info Commented-code block (6 lines) in inference/pipeline.py:54
info Commented-code block (5 lines) in inference/stages/load_prices.py:39

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

info Commented-code block (6 lines) in config.py:47

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/0200fcb3-4cf9-456d-bd20-bdce88f79ef1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0200fcb3-4cf9-456d-bd20-bdce88f79ef1/

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.