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.

YoavRubin00/finpl

https://github.com/YoavRubin00/finpl · scanned 2026-06-16 01:07 UTC (2 months, 1 week ago)

240 raw signals (0 security + 240 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 53 Low 36 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 240 Crowd 0 Layer: Api 1 Frontend 15 Security 15 Cicd 2 Quality 207

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.

Legacy markers 1 finding

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.

1 matching finding on this repo

low Stray `console.log` in TS/JS — scripts/test-legacy-local-state.ts:7

View all legacy markers findings →

Commented-out code 145 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 api/ai/stock-analyze-deep.ts:81
info Commented-code block (7 lines) in api/auth/verify.ts:97
info Commented-code block (6 lines) in api/_shared/sendDailyEmails.ts:91
info Commented-code block (5 lines) in scripts/migrate-local.mjs:1
info Commented-code block (8 lines) in scripts/vercel-dev-local.mjs:4
info Commented-code block (5 lines) in scripts/db-diagram.mjs:4
info Commented-code block (8 lines) in app/tower-defense-boss.tsx:12
info Commented-code block (5 lines) in app/_layout.tsx:233
info Commented-code block (5 lines) in app/interstitial/bullshit-ch0.tsx:87
info Commented-code block (6 lines) in app/api/sync/profile+api.ts:169
info Commented-code block (5 lines) in app/api/email/track-click+api.ts:9
info Commented-code block (5 lines) in app/api/ai/payslip-analyze+api.ts:388

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

medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/settings.json .claude/settings.json:23
low Old/deprecated-named symbol `streak_repair_offer_v1` in src/features/bandit/ban…
info Commented-code block (6 lines) in src/features/pearls/pearlConfig.ts:99
info Commented-code block (5 lines) in src/features/chapter-1-content/moduleIntroCon…

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/67504f26-e285-4350-b32a-82ca57771e34/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/67504f26-e285-4350-b32a-82ca57771e34/

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.