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.

multica

https://github.com/multica-ai/multica · scanned 2026-05-17 02:50 UTC (13 hours, 30 minutes ago) · 10 languages

761 findings (52 legacy + 709 scanner) 2nd percentile · Typescript · large (100-500K LoC) Scanner says 63 (lower by 6)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 13 hours, 30 minutes ago · v2 · 407 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Severity distribution — click a segment to filter
Active filters: severity: critical × excluding tests × Reset all
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 63.3/100 with 100.0% coverage. It contains 4685 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 355 findings — concentrated in quality (164), frontend (94), software (50). Risk profile is high: 0 critical, 1 high, 35 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 12 of 407 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Legacy security credential_exposure conf 0.90 [SEC001] Hardcoded Password: Hardcoded password found in source code.
Use environment variables or a secrets manager.
scripts/ensure-postgres.sh:19 credential_exposurelegacy
critical Legacy security credential_exposure conf 1.00 [SEC022] Database URL With Embedded Credential: A database connection URL contains an embedded username and password. These URLs are often copied into defaults, docs, and scripts, then leak working credentials.
Remove the embedded password, require the URL from a secret store or environment variable, and rotate the database credential.
server/cmd/backfill_task_usage_daily/main.go:49 credential_exposurelegacy
critical Legacy security credential_exposure conf 1.00 [SEC022] Database URL With Embedded Credential: A database connection URL contains an embedded username and password. These URLs are often copied into defaults, docs, and scripts, then leak working credentials.
Remove the embedded password, require the URL from a secret store or environment variable, and rotate the database credential.
scripts/screenshot-pr-cards.mjs:14 credential_exposurelegacy
critical Legacy security credential_exposure conf 1.00 [SEC022] Database URL With Embedded Credential: A database connection URL contains an embedded username and password. These URLs are often copied into defaults, docs, and scripts, then leak working credentials.
Remove the embedded password, require the URL from a secret store or environment variable, and rotate the database credential.
scripts/init-worktree-env.sh:31 credential_exposurelegacy
critical Legacy cicd docker conf 0.96 Compose service contains a literal secret environment value
Literal secrets in Compose files are committed to source and exposed through container inspection.
docker-compose.yml:3 dockerlegacy
critical Legacy security auth conf 0.88 Token handoff appears to use a callback URL or fragment
A frontend flow appears to combine a caller-controlled callback/redirect parameter with a token-bearing URL or fragment. This can exfiltrate sessions when callback validation is incomplete.
apps/desktop/src/main/index.ts:69 authlegacy
critical Legacy security auth conf 0.88 Token handoff appears to use a callback URL or fragment
A frontend flow appears to combine a caller-controlled callback/redirect parameter with a token-bearing URL or fragment. This can exfiltrate sessions when callback validation is incomplete.
packages/views/auth/login-page.tsx:70 authlegacy
critical Legacy security auth conf 0.88 Token handoff appears to use a callback URL or fragment
A frontend flow appears to combine a caller-controlled callback/redirect parameter with a token-bearing URL or fragment. This can exfiltrate sessions when callback validation is incomplete.
apps/web/app/(auth)/login/page.tsx:174 authlegacy
critical Legacy security auth conf 0.88 Token handoff appears to use a callback URL or fragment
A frontend flow appears to combine a caller-controlled callback/redirect parameter with a token-bearing URL or fragment. This can exfiltrate sessions when callback validation is incomplete.
apps/web/app/(auth)/login/page.tsx:75 authlegacy
critical Legacy security auth conf 0.88 Token handoff appears to use a callback URL or fragment
A frontend flow appears to combine a caller-controlled callback/redirect parameter with a token-bearing URL or fragment. This can exfiltrate sessions when callback validation is incomplete.
apps/desktop/src/renderer/src/App.tsx:51 authlegacy
critical Legacy security auth conf 0.88 Token handoff appears to use a callback URL or fragment
A frontend flow appears to combine a caller-controlled callback/redirect parameter with a token-bearing URL or fragment. This can exfiltrate sessions when callback validation is incomplete.
apps/web/app/auth/callback/page.tsx:127 authlegacy
critical Legacy security auth conf 0.88 Token handoff appears to use a callback URL or fragment
A frontend flow appears to combine a caller-controlled callback/redirect parameter with a token-bearing URL or fragment. This can exfiltrate sessions when callback validation is incomplete.
apps/web/app/auth/callback/page.tsx:44 authlegacy
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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.