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.

quantchat-yy/Quant-Ecosystem

https://github.com/quantchat-yy/Quant-Ecosystem · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

889 raw signals (0 security + 889 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 875 actionable findings from 1 signal source. 14 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 · 875 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 279 Medium 147 Low 244 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 875 Crowd 0 Layer: Software 3 Frontend 186 Network 3 Hardware 2 Security 24 Cicd 2 Quality 327 Api 328

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

2 matching findings on this repo

low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 100 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

info `truncate` class without `title=` for hover reveal — apps/quantsync/src/legacy-…
low Icon-only button without accessible name — apps/quantsync/src/legacy-pages/comp…
info `truncate` class without `title=` for hover reveal — apps/quantsync/src/legacy-…
info `truncate` class without `title=` for hover reveal — apps/quantsync/src/legacy-…
medium `fetch()` without try/.catch or AbortSignal — apps/quantsync/src/legacy-pages/s…
medium `fetch()` without try/.catch or AbortSignal — apps/quantsync/src/legacy-pages/a…
medium `fetch()` without try/.catch or AbortSignal — apps/quantsync/src/legacy-pages/m…
medium `fetch()` without try/.catch or AbortSignal — apps/quantsync/src/legacy-pages/i…
medium `fetch()` without try/.catch or AbortSignal — apps/quantsync/src/legacy-pages/c…
medium `fetch()` without try/.catch or AbortSignal — apps/quantsync/src/legacy-pages/l…
medium `fetch()` without try/.catch or AbortSignal — apps/quantsync/src/legacy-pages/s…
medium `fetch()` without try/.catch or AbortSignal — apps/quantsync/src/legacy-pages/t…

View all legacy markers findings →

Commented-out code 72 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 apps/quantneon/src/components/MiniGameLobby.t…
info Commented-code block (5 lines) in apps/quantneon/src/components/ShoppingTag.tsx…
info Commented-code block (5 lines) in apps/quantneon/src/components/ARTryOn.tsx:1
info Commented-code block (5 lines) in apps/quantneon/src/hooks/useFeed.ts:1
info Commented-code block (5 lines) in apps/quantneon/src/hooks/useReels.ts:1
info Commented-code block (5 lines) in apps/quantmax/src/components/SwipeStack.tsx:1
info Commented-code block (6 lines) in apps/quantmax/src/components/DateTimer.tsx:1
info Commented-code block (5 lines) in apps/quantmax/src/components/RandomMatcher.ts…
info Commented-code block (5 lines) in apps/quantmax/src/components/GiftPanel.tsx:1
info Commented-code block (6 lines) in apps/quantmax/src/components/VideoCreator.tsx…
info Commented-code block (5 lines) in apps/quantmax/src/pages/create.tsx:1
info Commented-code block (5 lines) in apps/quantmax/src/pages/challenges.tsx:1

View all commented-out code findings →

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

2 matching findings on this repo

low Node manifest has dependencies but no lockfile: packages/edge-config/package.js… packages/edge-config/package.json
medium `fetch()` without try/.catch or AbortSignal — apps/quantai/src/app/api/ecosyste…

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/2371d84c-6dbb-4b68-b05b-e4bacfecc0e3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2371d84c-6dbb-4b68-b05b-e4bacfecc0e3/

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.