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.

vorreix/profitsync

https://github.com/vorreix/profitsync · scanned 2026-06-16 00:52 UTC (2 months, 1 week ago)

244 raw signals (0 security + 244 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 192 actionable findings from 1 signal source. 52 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 · 192 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 20 Medium 19 Low 22 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 192 Crowd 0 Layer: Frontend 59 Hardware 1 Security 5 Cicd 2 Quality 104 Api 21

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 Old/deprecated-named symbol `sk_live_legacy` in api/_lib/dodo.test.ts:44

View all legacy markers findings →

Commented-out code 79 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 playwright.config.ts:56
info Commented-code block (5 lines) in vite.config.ts:84
info Commented-code block (7 lines) in api/index.ts:7
info Commented-code block (10 lines) in api/ssr.ts:11
info Commented-code block (5 lines) in api/_ssr/markdown.ts:7
info Commented-code block (6 lines) in api/_routes/flow.ts:27
info Commented-code block (5 lines) in api/_routes/spaces.ts:11
info Commented-code block (5 lines) in api/_routes/notifications/preferences.ts:8
info Commented-code block (5 lines) in api/_routes/wealth/transfer.ts:54
info Commented-code block (5 lines) in api/_routes/wealth/accounts.ts:13
info Commented-code block (5 lines) in api/_routes/admin/worker.ts:4
info Commented-code block (5 lines) in api/_routes/admin/user-groups/[id]/members.ts…

View all commented-out code findings →

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

4 matching findings on this repo

high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:71
info Commented-code block (5 lines) in playwright.config.ts:56
info Commented-code block (5 lines) in vite.config.ts:84
info Commented-code block (5 lines) in pwa/pwa-assets.config.ts:7

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/d605be52-11bb-408f-aa1d-4273e8ec503a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d605be52-11bb-408f-aa1d-4273e8ec503a/

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.