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-v2

https://github.com/Arun-Sanjay/Titan-Protocol-v2 · scanned 2026-06-17 01:18 UTC (1 month, 2 weeks ago)

136 raw signals (0 security + 136 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 10 Medium 13 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 105 Crowd 0 Layer: Frontend 9 Security 11 Cicd 3 Quality 82

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 64 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 (6 lines) in jest.config.js:17
info Commented-code block (5 lines) in app/_layout.tsx:20
info Commented-code block (5 lines) in app/(tabs)/track.tsx:61
info Commented-code block (7 lines) in app/(tabs)/index.tsx:270
info Commented-code block (5 lines) in app/hub/workouts.tsx:1214
info Commented-code block (6 lines) in app/hub/sleep.tsx:44
info Commented-code block (5 lines) in app/hub/settings.tsx:400
info Commented-code block (8 lines) in app/(auth)/login.tsx:53
info Commented-code block (5 lines) in app/(auth)/email-login.tsx:65
info Commented-code block (5 lines) in app/(auth)/signup.tsx:72
info Commented-code block (5 lines) in src/hooks/queries/useProfile.ts:109
info Commented-code block (6 lines) in src/components/v2/walkthrough/WalkthroughSumm…

View all commented-out code findings →

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

6 matching findings on this repo

high Agent instruction/config may expose a secret: web/CLAUDE.md web/CLAUDE.md:428
high Agent instruction/config may expose a secret: web/.claude/skills/titan-web/skil… web/.claude/skills/titan-web/skill.md:177
high Agent instruction/config may expose a secret: mobile-saas/.claude/skills/titan-… mobile-saas/.claude/skills/titan-mobile-saas/SKIL…:116
high Agent instruction/config may expose a secret: .claude/skills/titan-dev/SKILL.md .claude/skills/titan-dev/SKILL.md:131
info Commented-code block (6 lines) in jest.config.js:17
info Commented-code block (5 lines) in web/eslint.config.mjs:1

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/cfded922-279c-4ab6-bc7f-325bdee8af31/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cfded922-279c-4ab6-bc7f-325bdee8af31/

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.