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.

YH-05/quants

https://github.com/YH-05/quants · scanned 2026-06-16 01:06 UTC (2 months, 1 week ago)

342 raw signals (0 security + 342 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 9 Medium 163 Low 97 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 316 Crowd 0 Layer: Software 23 Api 1 Hardware 4 Frontend 1 Security 11 Cicd 4 Quality 272

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 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 3 places repo-level
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 5 places

View all duplicates & near-duplicates findings →

Commented-out code 37 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 (7 lines) in notebook/ca_strategy_buyhold_analysis.py:1
info Commented-code block (7 lines) in notebook/ca_strategy_us_only_analysis.py:1
info Commented-code block (7 lines) in notebook/ca_strategy_phase6_analysis.py:1
info Commented-code block (6 lines) in notebook/reporting/Market-Report2.py:70
info Commented-code block (10 lines) in notebook/FILING_NLP/pipeline/embed_indices.p…
info Commented-code block (5 lines) in tests/database/unit/test_parquet_schema.py:29
info Commented-code block (6 lines) in tests/dev/ca_strategy/unit/test_return_calcul…
info Commented-code block (5 lines) in tests/market/fraser/integration/test_fraser_i…
info Commented-code block (5 lines) in tests/news/integration/test_orchestrator_call…
info Commented-code block (13 lines) in src_sample/database_utils.py:40
info Commented-code block (5 lines) in src_sample/weekly_report_generator.py:96
info Commented-code block (7 lines) in src_sample/ROIC_make_data_files.py:703

View all commented-out code findings →

Config drift 12 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/sync-config.yaml .claude/sync-config.yaml:12
medium Agent authority lacks a verifier contract: .claude/sync-config.yaml .claude/sync-config.yaml
medium Agent authority lacks a verifier contract: .claude/commands/sync-claude-config.… .claude/commands/sync-claude-config.md
high Agent instruction/config may expose a secret: .claude/commands/new-package.md .claude/commands/new-package.md:224
high Agent instruction/config may expose a secret: .claude/agents/implementation-val… .claude/agents/implementation-validator.md:367
high Agent instruction/config may expose a secret: .claude/agents/pr-security-code.md .claude/agents/pr-security-code.md:53
high Agent instruction/config may expose a secret: .claude/agents/security-scanner.md .claude/agents/security-scanner.md:145
high Agent instruction/config may expose a secret: .claude/skills/coding-standards/g… .claude/skills/coding-standards/guide.md:581
medium Agent authority lacks a verifier contract: .claude/skills/sync-claude-config/SK… .claude/skills/sync-claude-config/SKILL.md
high Agent instruction/config may expose a secret: .claude/skills/project-management… .claude/skills/project-management/guide.md:294
high Agent instruction/config may expose a secret: .claude/skills/scan/SKILL.md .claude/skills/scan/SKILL.md:321
low Old/deprecated-named symbol `FILING_NLP_v2` in notebook/FILING_NLP/pipeline/con…

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/db950c62-f0c7-4d12-af9a-394d1e8c16b1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/db950c62-f0c7-4d12-af9a-394d1e8c16b1/

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.