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.

Arun-Sanjay/titan-protocol-mobile-saas

https://github.com/Arun-Sanjay/titan-protocol-mobile-saas · scanned 2026-06-17 01:17 UTC (1 month, 2 weeks ago)

31 raw signals (0 security + 31 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -8.7 (diff) · 31 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 31 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 6 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 31 Crowd 0 Layer: Api 1 Frontend 2 Security 2 Cicd 2 Quality 24

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.

Commented-out code 17 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 app/(tabs)/profile.tsx:147
info Commented-code block (5 lines) in app/(auth)/signup.tsx:61
info Commented-code block (5 lines) in src/sync/restore.ts:81
info Commented-code block (5 lines) in src/sync/flush-dirty.ts:115
info Commented-code block (5 lines) in src/stores/useAuthStore.ts:128
info Commented-code block (5 lines) in src/components/FirstRunPullGate.tsx:50
info Commented-code block (8 lines) in src/db/gamification.ts:3
info Commented-code block (5 lines) in src/db/sqlite/service-helpers.ts:516
info Commented-code block (7 lines) in src/db/sqlite/column-types.ts:7
info Commented-code block (5 lines) in src/db/sqlite/migrator.ts:32
info Commented-code block (5 lines) in src/db/sqlite/migrations/004_add_xp_log.ts:1
info Commented-code block (5 lines) in src/lib/protocol-integrity.ts:147

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

high Agent instruction/config may expose a secret: .claude/skills/titan-mobile-saas/… .claude/skills/titan-mobile-saas/SKILL.md:116

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/4086b8da-8dfc-46d1-b991-ebf852b259fc/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4086b8da-8dfc-46d1-b991-ebf852b259fc/

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.