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.

arun7296/apex

https://github.com/arun7296/apex · scanned 2026-06-17 01:38 UTC (1 month, 2 weeks ago)

772 raw signals (0 security + 772 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 4 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.
4 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 32 places
  • low Near-duplicate function bodies in 3 places repo-level
View all duplicates & near-duplicates findings →
Legacy markers 152 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.
12 matching findings on this repo
  • low Stray `console.log` in TS/JS — legacy/frontend/scripts/generate-sw.js:53
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/app/si…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/app/jo…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/compon…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/compon…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/compon…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/compon…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/compon…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/compon…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/compon…
  • info `truncate` class without `title=` for hover reveal — legacy/frontend/src/compon…
  • medium `dangerouslySetInnerHTML` used in a React component — legacy/frontend/src/compo…
View all legacy markers findings →
Commented-out code 349 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 apex_live_control.py:81
  • info Commented-code block (5 lines) in apex_common.py:206
  • info Commented-code block (6 lines) in position_tracker.py:332
  • info Commented-code block (7 lines) in apex_dashboard.py:73
  • info Commented-code block (7 lines) in apex_db.py:79
  • info Commented-code block (5 lines) in ic_backtest_engine.py:52
  • info Commented-code block (6 lines) in kite_trade_reconciler.py:171
  • info Commented-code block (5 lines) in order_builder.py:242
  • info Commented-code block (7 lines) in apex_api.py:49
  • info Commented-code block (8 lines) in insider_promoter_tracker.py:155
  • info Commented-code block (7 lines) in cron_health_audit.py:55
  • info Commented-code block (6 lines) in apex_datahub_bootstrap.py:237
View all commented-out code findings →
Config drift 14 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.
12 matching findings on this repo
  • high Agent instruction/config may expose a secret: .claude/agents/streamlit-dashboar… .claude/agents/streamlit-dashboard-engineer.md:71
  • low Old/deprecated-named symbol `swing_v2` in apex_datahub_producers/five_pct_scree…
  • info Commented-code block (8 lines) in apex_datahub_producers/five_pct_screener/conf…
  • info Commented-code block (6 lines) in frontend/eslint.config.mjs:3
  • info Commented-code block (6 lines) in apex_options_engine/logging_config.py:90
  • info Commented-code block (6 lines) in apex_options_engine/risk/sizing_config.py:12
  • info Commented-code block (6 lines) in apex_options_engine/config/live_mode_reader.p…
  • info Commented-code block (5 lines) in apex_options_engine/config/paper_observation.…
  • info Commented-code block (6 lines) in apex_options_engine/config/strategy_to_class.…
  • info Commented-code block (5 lines) in apex_options_engine/config/strategy_threshold…
  • info Commented-code block (6 lines) in apex_options_engine/config/picker_thresholds.…
  • info Commented-code block (5 lines) in apex_mcx/config.py:142
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/412776d8-c4ee-4342-9731-bd89c1b36a84/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/412776d8-c4ee-4342-9731-bd89c1b36a84/

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.