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.

wtsaleksandr-lang/wefixtrades

https://github.com/wtsaleksandr-lang/wefixtrades · scanned 2026-06-16 01:01 UTC (2 months, 1 week ago)

1122 raw signals (0 security + 1122 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 58 Medium 252 Low 332 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1010 Crowd 0 Layer: Frontend 266 Security 53 Cicd 3 Quality 582 Api 106

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 2 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.

2 matching findings on this repo

low Old/deprecated-named symbol `monthlyLegacy` in server/lib/stripePriceResolver.t…
low Old/deprecated-named symbol `WizardLegacy` in server/jobs/trialLifecycleWorker.…

View all legacy markers findings →

Commented-out code 284 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 lighthouserc.cjs:72
info Commented-code block (5 lines) in client/public/widget/v1.js:12
info Commented-code block (9 lines) in client/src/config/products.ts:117
info Commented-code block (6 lines) in client/src/components/CheckoutModal.tsx:122
info Commented-code block (5 lines) in client/src/components/contentflow/ContentFlow…
info Commented-code block (5 lines) in client/src/components/ai/AIChatBubble.tsx:73
info Commented-code block (5 lines) in client/src/components/shared/AppErrorBoundary…
info Commented-code block (9 lines) in client/src/components/shared/TemplateThumbnai…
info Commented-code block (5 lines) in client/src/components/ui/navbar-menu.tsx:20
info Commented-code block (5 lines) in client/src/components/ui/visual-primitives/Sp…
info Commented-code block (6 lines) in client/src/components/ui/visual-primitives/Kp…
info Commented-code block (7 lines) in client/src/components/ui/visual-primitives/AI…

View all commented-out code findings →

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

9 matching findings on this repo

medium Insecure pattern 'node_child_process' in audit.config.ts:2 audit.config.ts:2
medium Insecure pattern 'node_child_process' in playwright.config.ts:2 playwright.config.ts:2
medium Insecure pattern 'node_child_process' in smoke.config.ts:14 smoke.config.ts:14
medium Runtime service client appears to use placeholder configuration
info Commented-code block (9 lines) in client/src/config/products.ts:117
info Commented-code block (5 lines) in client/src/components/wizard/elfsight/imageTe…
info Commented-code block (7 lines) in client/src/components/wizard/elfsight/buildAd…
info Commented-code block (10 lines) in client/src/components/wizard/elfsight/buildL…
info Commented-code block (8 lines) in scripts/db/drizzle.config.dev.ts:40

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/ad933603-80ca-445f-a8ff-b30b61811c55/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ad933603-80ca-445f-a8ff-b30b61811c55/

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.