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.

xang1234/stock-screener

https://github.com/xang1234/stock-screener · scanned 2026-06-16 01:02 UTC (2 months, 1 week ago)

330 raw signals (0 security + 330 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 295 actionable findings from 1 signal source. 35 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 · 295 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 97 Medium 16 Low 136 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 295 Crowd 0 Layer: Software 12 Frontend 1 Network 3 Hardware 5 Security 101 Cicd 3 Quality 120 Api 50

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

7 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 11 places
low Near-duplicate function bodies in 13 places

View all duplicates & near-duplicates findings →

Legacy markers 12 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 Old/deprecated-named symbol `TestFromLegacy` in backend/tests/unit/test_univers…
low Old/deprecated-named symbol `used_legacy` in backend/tests/unit/test_universe_c…
low Old/deprecated-named symbol `test_build_universe_def_raises_on_invalid_legacy` …
low Old/deprecated-named symbol `vcp_detected_by_legacy` in backend/tests/unit/test…
low Old/deprecated-named symbol `TestUnboundScanFallsBackToLegacy` in backend/tests…
low Old/deprecated-named symbol `s_legacy` in backend/tests/unit/test_scan_crud_end…
low Old/deprecated-named symbol `vcp_detected_by_legacy` in backend/tests/unit/gold…
low Old/deprecated-named symbol `_query_legacy` in backend/tests/parity/test_scan_p…
low Old/deprecated-named symbol `used_legacy` in backend/app/api/v1/scans.py:169
low Old/deprecated-named symbol `distance_to_pivot_pct_legacy` in backend/app/analy…
low Old/deprecated-named symbol `used_legacy` in backend/app/services/universe_comp…
low Old/deprecated-named symbol `from_legacy` in backend/app/schemas/universe.py:306

View all legacy markers findings →

Commented-out code 43 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 frontend/src/App.jsx:101
info Commented-code block (5 lines) in frontend/src/components/Stock/MarketThemesLis…
info Commented-code block (5 lines) in frontend/src/components/Charts/rsBand.js:1
info Commented-code block (5 lines) in frontend/src/components/Charts/useDragZoom.js…
info Commented-code block (5 lines) in frontend/src/components/Charts/CandlestickCha…
info Commented-code block (5 lines) in frontend/src/components/Scan/ChartViewerModal…
info Commented-code block (5 lines) in backend/tests/unit/test_provider_snapshot_ser…
info Commented-code block (5 lines) in backend/tests/unit/test_translation_service.p…
info Commented-code block (6 lines) in backend/tests/unit/test_multilingual_qa_harne…
info Commented-code block (5 lines) in backend/tests/unit/test_scan_field_availabili…
info Commented-code block (5 lines) in backend/tests/load/conftest.py:21
info Commented-code block (6 lines) in backend/tests/load/measurement.py:21

View all commented-out code findings →

Config drift 4 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.

4 matching findings on this repo

info Commented-code block (6 lines) in backend/app/config/settings.py:165
low Unused endpoint: GET /config/llm
low Unused endpoint: POST /config/llm
low Unused endpoint: POST /config/ollama

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/a8cbe6a5-d86e-45c1-a96c-42556b3e6efa/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a8cbe6a5-d86e-45c1-a96c-42556b3e6efa/

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.