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.
Sign up free Scan another repo

z569045281/qbts-quant-lab

https://github.com/z569045281/qbts-quant-lab · scanned 2026-06-16 01:10 UTC (2 months, 1 week ago)

58 raw signals (0 security + 58 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 57 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
56.2
/100
Security checks
56
0 findings
System graph
56
100.0% cov · 57 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 8 Medium 6 Low 40 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 57 Crowd 0 Layer: Software 15 Frontend 3 Security 8 Cicd 2 Quality 15 Api 14
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 56.2/100 with 100.0% coverage. It contains 324 nodes across 18 cross-layer flows, written primarily in mixed languages. Engine surfaced 58 findings — concentrated in quality (16), software (15), api (14). Risk profile is high: 0 critical, 8 high, 6 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 54 of 57 actionable findings. 58 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security auth conf 1.00 FastAPI POST `admin_reset` without auth dependency — backend/api.py:594
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api.py:594 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_brief` without auth dependency — backend/api.py:1037
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api.py:1037 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_decision` without auth dependency — backend/api.py:1081
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api.py:1081 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `toggle_favorite` without auth dependency — backend/api.py:617
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api.py:617 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'exec_used' in backend/api.py:666
Found a known-risky pattern (exec_used). Review and replace if possible.
backend/api.py:666 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in backend/execution/trader.py:143
Found a known-risky pattern (exec_used). Review and replace if possible.
backend/execution/trader.py:143 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in backend/factors/generator.py:309
Found a known-risky pattern (exec_used). Review and replace if possible.
backend/factors/generator.py:309 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in backend/factors/ml_factor.py:104
Found a known-risky pattern (exec_used). Review and replace if possible.
backend/factors/ml_factor.py:104 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/app/_lib/data.ts:283
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/app/mine/page.tsx:697
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, tests. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/deploy-pages.yml CI/CD securitySupply chainGithub actions
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 50 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/deploy-pages@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/deploy-pages.yml:60 CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/app/mine/page.tsx:318
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Tests conf 1.00 Low test-to-source ratio
4 tests / 38 src (ratio 0.11).
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/factors/generator.py:generate_and_validate, backend/factors/generator.py:generate_and_validate_ml This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why t…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/dashboard/holdings.py:get_holdings_signal, backend/dashboard/reddit.py:fetch_reddit_signal, backend/dashboard/intraday.py:get_intraday_signal This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_and_validate_ml
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/factors/generator.py:565
low System graph software Dead code conf 1.00 Possibly dead Python function: grade_pending
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/journal.py:87
low System graph software Dead code conf 1.00 Possibly dead Python function: grade_predictions
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/calibration.py:97
low System graph software Dead code conf 1.00 Possibly dead Python function: load_dataframe
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_pipeline.py:65
low System graph software Dead code conf 1.00 Possibly dead Python function: load_recent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/journal.py:194
low System graph software Dead code conf 1.00 Possibly dead Python function: record
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/journal.py:60
low System graph software Dead code conf 1.00 Possibly dead Python function: run_all_strategies
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:424
low System graph software Dead code conf 1.00 Possibly dead Python function: strategy_52w_breakout
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:329
low System graph software Dead code conf 1.00 Possibly dead Python function: strategy_connors_rsi2
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:79
low System graph software Dead code conf 1.00 Possibly dead Python function: strategy_gap_fade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:290
low System graph software Dead code conf 1.00 Possibly dead Python function: strategy_news_overreaction
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:369
low System graph software Dead code conf 1.00 Possibly dead Python function: strategy_peer_lead_lag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:245
low System graph software Dead code conf 1.00 Possibly dead Python function: strategy_pre_earnings_drift
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:204
low System graph software Dead code conf 1.00 Possibly dead Python function: strategy_short_squeeze
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:121
low System graph software Dead code conf 1.00 Possibly dead Python function: strategy_vix_contrarian
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/dashboard/strategies.py:165
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: GET /dashboard/calibration
`backend/api.py` declares `GET /dashboard/calibration` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /dashboard/snapshot
`backend/api.py` declares `GET /dashboard/snapshot` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /factors/{factor_id}/chart
`backend/api.py` declares `GET /factors/{factor_id}/chart` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /factors/{factor_id}/code
`backend/api.py` declares `GET /factors/{factor_id}/code` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /leaderboard
`backend/api.py` declares `GET /leaderboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /mining/stream
`backend/api.py` declares `GET /mining/stream` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /quote/live
`backend/api.py` declares `GET /quote/live` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /today/signals
`backend/api.py` declares `GET /today/signals` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /trading/execute
`backend/api.py` declares `GET /trading/execute` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /trading/status
`backend/api.py` declares `GET /trading/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/reset
`backend/api.py` declares `POST /admin/reset` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /dashboard/brief/refresh
`backend/api.py` declares `POST /dashboard/brief/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /dashboard/decision/refresh
`backend/api.py` declares `POST /dashboard/decision/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /factors/{factor_id}/favorite
`backend/api.py` declares `POST /factors/{factor_id}/favorite` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/api.py (1268 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/app/mine/page.tsx (1389 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/68da098e-d183-4e85-ba1d-5083df8db16c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/68da098e-d183-4e85-ba1d-5083df8db16c/

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.