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.

yourpersonalagent/ypa

https://github.com/yourpersonalagent/ypa · scanned 2026-06-16 01:08 UTC (2 months, 1 week ago)

662 raw signals (0 security + 662 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 662 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 662 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 7 Medium 121 Low 112 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 662 Crowd 0 Layer: Software 15 Frontend 31 Network 1 Security 59 Quality 499 Api 57

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.

Duplicates & near-duplicates 1 finding

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

Legacy markers 5 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

5 matching findings on this repo

low Old/deprecated-named symbol `hydrateFromLegacy` in frontend/src/main.ts:104
low Old/deprecated-named symbol `hydrateFromLegacy` in frontend/src/stores/appStore…
low Old/deprecated-named symbol `hydrateFromLegacy` in frontend/src/stores/graphSto…
low Old/deprecated-named symbol `sendViaLegacy` in frontend/src/chat/ChatInput.tsx:…
low Old/deprecated-named symbol `migrateLegacy` in bridge/mcp/knowledge-server.js:1…

View all legacy markers findings →

Commented-out code 416 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 frontend/vite.config.js:21
info Commented-code block (5 lines) in frontend/src/api.ts:1
info Commented-code block (5 lines) in frontend/src/branding.ts:3
info Commented-code block (5 lines) in frontend/src/ShutdownOverlay.tsx:1
info Commented-code block (6 lines) in frontend/src/ViewOverlay.tsx:62
info Commented-code block (5 lines) in frontend/src/KeyboardShortcuts.tsx:324
info Commented-code block (8 lines) in frontend/src/color-themes-config.ts:18
info Commented-code block (5 lines) in frontend/src/store.ts:45
info Commented-code block (5 lines) in frontend/src/ErrorBoundary.tsx:6
info Commented-code block (7 lines) in frontend/src/bg-themes.ts:1
info Commented-code block (7 lines) in frontend/src/Shell.tsx:3
info Commented-code block (5 lines) in frontend/src/AppEffects.tsx:15

View all commented-out code findings →

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

12 matching findings on this repo

low Stray `console.log` in TS/JS — bridge/config/harness-routes.ts:251
low Very large file: bridge/config/config-core-routes.ts (1106 lines)
medium Runtime service client appears to use placeholder configuration
info Commented-code block (6 lines) in frontend/vite.config.js:21
info Commented-code block (8 lines) in frontend/src/color-themes-config.ts:18
info Commented-code block (5 lines) in frontend/src/design-themes-config.ts:18
info Commented-code block (6 lines) in bridge/models/config.ts:8
info Commented-code block (5 lines) in bridge/config/provider-presets.ts:1
info Commented-code block (5 lines) in bridge/config/paths.ts:1
info Commented-code block (5 lines) in bridge/config/presets-routes.ts:1
info Commented-code block (5 lines) in bridge/config/files-routes.ts:10
info Commented-code block (6 lines) in bridge/config/skills-helpers.ts: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/cfde0d7a-341d-4c19-a016-78e475a1d577/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cfde0d7a-341d-4c19-a016-78e475a1d577/

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.