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.

AI-Isaiah/Quantalyze

https://github.com/AI-Isaiah/Quantalyze · scanned 2026-06-17 01:21 UTC (1 month, 2 weeks ago)

965 raw signals (0 security + 965 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -20.7 (diff) · 956 actionable findings from 1 signal source. 9 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 · 956 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 8 High 86 Medium 48 Low 129 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 956 Crowd 0 Layer: Software 1 Frontend 36 Network 1 Hardware 2 Security 30 Cicd 1 Quality 804 Api 81

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 14 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 `verification_requests_legacy` in src/app/api/verif…
low Old/deprecated-named symbol `migrateLegacy` in src/app/(dashboard)/allocations/…
low Old/deprecated-named symbol `emitFirstBridgeSurfacedLegacy` in src/lib/analytic…
low Old/deprecated-named symbol `migrateLegacy` in src/lib/storage/codecs.ts:52
low Old/deprecated-named symbol `migrateLegacy` in src/lib/storage/codecs.test.ts:15
low Old/deprecated-named symbol `runIntrospectionSqlLegacy` in src/__tests__/match-…
low Old/deprecated-named symbol `boLegacy` in src/__tests__/bridge-outcome-cron-hol…
low Old/deprecated-named symbol `_claim_legacy` in analytics-service/main_worker.py…
low Old/deprecated-named symbol `verification_requests_legacy` in analytics-service…
low Old/deprecated-named symbol `_claim_legacy` in analytics-service/tests/test_com…
low Old/deprecated-named symbol `verification_requests_legacy` in analytics-service…
info Commented-code block (7 lines) in analytics-service/tests/test_verify_strategy_…

View all legacy markers findings →

Commented-out code 660 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 (10 lines) in vitest.config.ts:6
info Commented-code block (8 lines) in eslint.config.mjs:33
info Commented-code block (10 lines) in next.config.ts:24
info Commented-code block (9 lines) in tests/a11y/wizard-contrast.test.ts:54
info Commented-code block (5 lines) in tests/a11y/trust-tier-tokens.test.ts:48
info Commented-code block (6 lines) in tests/a11y/chart-contrast.test.ts:101
info Commented-code block (5 lines) in tests/integration/mig-129-cutover-concurrency…
info Commented-code block (7 lines) in tests/integration/mig-128-batch-concurrency.t…
info Commented-code block (6 lines) in tests/integration/phase-19-pra-write.test.ts:…
info Commented-code block (6 lines) in tests/integration/cron-flag-monitor.test.ts:5…
info Commented-code block (6 lines) in tests/integration/process-key-thin-adapters.t…
info Commented-code block (5 lines) in tests/lib/wizard-errors-shape.test.ts:42

View all commented-out code findings →

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

7 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
info Commented-code block (10 lines) in vitest.config.ts:6
info Commented-code block (8 lines) in eslint.config.mjs:33
info Commented-code block (10 lines) in next.config.ts:24
info Commented-code block (5 lines) in src/app/factsheet/[id]/v2/chart-configs.ts:237
info Commented-code block (9 lines) in analytics-service/tests/test_logging_config.p…
info Commented-code block (11 lines) in analytics-service/services/logging_config.py…

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/39ce0f62-382a-45eb-ac42-1985c5079bde/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/39ce0f62-382a-45eb-ac42-1985c5079bde/

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.