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.

aiagency40240157-web/Mystical

https://github.com/aiagency40240157-web/Mystical · scanned 2026-06-17 01:30 UTC (1 month, 2 weeks ago)

60 raw signals (0 security + 60 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -30.2 (diff) · 56 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 56 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 4 Medium 9 Low 39 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 56 Crowd 0 Layer: Frontend 8 Hardware 3 Security 6 Quality 11 Api 28

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in prisma/seed.ts

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in prisma/seed.ts:8; move to env var / secrets manager.

prisma/seed.ts:8

Possible secret in prisma/seed.ts

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in prisma/seed.ts:9; move to env var / secrets manager.

prisma/seed.ts:9

Possible secret in prisma/seed.ts

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in prisma/seed.ts:10; move to env var / secrets manager.

prisma/seed.ts:10

Possible secret in .claude/settings.local.json

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/settings.local.json:99; move to env var / secrets manager.

.claude/settings.local.json:99

Runtime dotenv file present in repo: frontend/.env.production

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/.env.production; move to env var / secrets manager.

frontend/.env.production

Runtime dotenv file present in repo: frontend/.env.development

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/.env.development; move to env var / secrets manager.

frontend/.env.development

Agent instruction/config may expose a secret: .claude/settings.local.json

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/settings.local.json:48; move to env var / secrets manager.

.claude/settings.local.json:48

Dangling fetch: POST https://graph.facebook.com/v18.0/${this.igBusinessId}/messages (src/modules/instagram/instagram.service.ts:116)

GapSeverity.HIGH Layer.API score 0.338

Why: high severity · contract mismatch FE↔BE

Fix: Confirm the FE call URL matches a backend endpoint; update one side.

Insecure pattern 'local_storage_auth_token' in frontend/src/lib/auth.ts:14

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

frontend/src/lib/auth.ts:14

#10

Dockerfile runs as root: Dockerfile

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/a33f31fa-e92a-4a26-a82c-6c4fbdc0bb11/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a33f31fa-e92a-4a26-a82c-6c4fbdc0bb11/

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.