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.

YOUSSEFELJAYAD/claude-fleet-portal

https://github.com/YOUSSEFELJAYAD/claude-fleet-portal · scanned 2026-06-16 01:08 UTC (2 months, 1 week ago)

182 raw signals (0 security + 182 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 182 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 · 182 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 33 Low 70 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 182 Crowd 0 Layer: Frontend 39 Network 2 Security 22 Cicd 3 Quality 63 Api 53

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 48 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 apps/web/vitest.config.ts:21
info Commented-code block (5 lines) in apps/web/test/setup.ts:11
info Commented-code block (5 lines) in apps/web/test/cov-chatthread-order.test.tsx:1…
info Commented-code block (6 lines) in apps/web/components/KanbanCard.tsx:79
info Commented-code block (8 lines) in apps/web/components/ChatThread.tsx:126
info Commented-code block (10 lines) in apps/web/components/ui.tsx:287
info Commented-code block (5 lines) in apps/web/app/projects/[id]/board/page.tsx:11
info Commented-code block (8 lines) in apps/web/app/chat/page.tsx:100
info Commented-code block (6 lines) in apps/web/lib/live.ts:216
info Commented-code block (5 lines) in apps/server/vitest.config.ts:3
info Commented-code block (6 lines) in apps/server/test/kanban.test.ts:25
info Commented-code block (6 lines) in apps/server/test/manager.test.ts:210

View all commented-out code findings →

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

5 matching findings on this repo

info Commented-code block (6 lines) in apps/web/vitest.config.ts:21
info Commented-code block (5 lines) in apps/server/vitest.config.ts:3
low Unused endpoint: GET /api/notifications/config
low Unused endpoint: PUT /api/notifications/config
low Unused endpoint: PUT /api/addons/:id/config

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/8f89e23f-f85c-4187-9d8f-744a6810b6bb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8f89e23f-f85c-4187-9d8f-744a6810b6bb/

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.