multica-ai/multica

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.

75 of your 167 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 15.62s · analysis 17.73s · 32.0 MB · GitHub API rate-limit (preflight)

https://github.com/multica-ai/multica · scanned 2026-06-09 04:34 UTC (19 hours, 20 minutes ago) · 10 languages

10675 raw signals (151 security + 10524 graph) 11/13 scanners ran 85th percentile · Typescript · large (100-500K LoC) System graph score 69 (higher by 16)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 19 hours, 19 minutes ago · v12 · 514 actionable findings from 2 signal sources. 136 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 · 464 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	95.0	0.20	19.00
`documentation_score`	83.0	0.15	12.45
`practices_score`	84.0	0.15	12.60
`code_quality`	70.0	0.10	7.00
Overall		1.00	85.0

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 15 Medium 28 Low 98 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 50 System graph 464 Crowd 0 Layer: Cicd 8 Quality 316 Software 57 Security 18 Api 1 Frontend 111 Hardware 3

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.

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `skipped_legacy` in apps/web/test/helpers.tsx:15

View all legacy markers findings →

Commented-out code 242 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/docs/middleware.ts:29
info Commented-code block (7 lines) in apps/docs/components/mermaid.tsx:27
info Commented-code block (5 lines) in apps/docs/app/layout.config.tsx:4
info Commented-code block (5 lines) in apps/docs/app/api/search/route.ts:4
info Commented-code block (6 lines) in apps/docs/lib/locale-link.ts:3
info Commented-code block (5 lines) in apps/desktop/src/renderer/src/App.tsx:24
info Commented-code block (6 lines) in apps/desktop/src/renderer/src/platform/i18n-a…
info Commented-code block (6 lines) in apps/desktop/src/renderer/src/platform/naviga…
info Commented-code block (5 lines) in apps/desktop/src/renderer/src/platform/naviga…
info Commented-code block (5 lines) in apps/desktop/src/renderer/src/components/page…
info Commented-code block (6 lines) in apps/desktop/src/renderer/src/components/desk…
info Commented-code block (8 lines) in apps/desktop/src/renderer/src/components/work…

View all commented-out code findings →

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

low File has no detected symbols: playwright.config.ts
low File has no detected symbols: apps/docs/source.config.ts
low File has no detected symbols: apps/docs/vitest.config.ts
low File has no detected symbols: apps/desktop/electron.vite.config.ts
low File has no detected symbols: apps/desktop/vitest.config.ts
low File has no detected symbols: apps/desktop/src/shared/runtime-config.test.ts
low File has no detected symbols: apps/desktop/src/main/runtime-config-loader.test.…
low File has no detected symbols: apps/mobile/metro.config.js
low File has no detected symbols: apps/mobile/babel.config.js
low File has no detected symbols: apps/mobile/tailwind.config.js
low File has no detected symbols: apps/mobile/app.config.ts
low File has no detected symbols: apps/mobile/eslint.config.js

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/a3a23df1-c446-4e56-a160-ed8bb6252f50/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a3a23df1-c446-4e56-a160-ed8bb6252f50/

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.