wecode-ai/Wegent

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.

252 of your 501 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 10.35s · analysis 50.67s · 39.0 MB · GitHub API rate-limit (preflight)

https://github.com/wecode-ai/Wegent · scanned 2026-06-05 13:05 UTC (5 days, 9 hours ago) · 10 languages

1949 raw signals (465 security + 1484 graph) 11/13 scanners ran 76th percentile · Python · huge (>500K LoC) System graph score 62 (higher by 26)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 9 hours ago · v2 · 796 actionable findings from 2 signal sources. 411 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 · 636 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	90.0	0.15	13.50
`code_quality`	45.0	0.10	4.50
Overall		1.00	87.0

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 8 High 147 Medium 71 Low 252 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 160 System graph 636 Crowd 0 Layer: Quality 300 Security 130 Cicd 16 Software 74 Frontend 209 Hardware 15 Api 52

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 4 findings

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.

4 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 9 places

View all duplicates & near-duplicates findings →

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 `refs_legacy` in backend/app/services/knowledge/tas…

View all legacy markers findings →

Commented-out code 76 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 frontend/playwright.config.ts:144
info Commented-code block (5 lines) in frontend/src/utils/userPreferences.ts:137
info Commented-code block (7 lines) in frontend/src/components/common/EnhancedMarkdo…
info Commented-code block (5 lines) in frontend/src/contexts/SocketContext.tsx:233
info Commented-code block (5 lines) in frontend/src/app/(tasks)/generate/GeneratePag…
info Commented-code block (5 lines) in frontend/src/app/(tasks)/generate/GeneratePag…
info Commented-code block (5 lines) in frontend/src/app/(tasks)/knowledge/[namespace…
info Commented-code block (6 lines) in frontend/src/lib/telemetry/FrontendTracer.ts:…
info Commented-code block (5 lines) in frontend/src/hooks/useTypewriter.ts:43
info Commented-code block (5 lines) in frontend/src/features/settings/components/Git…
info Commented-code block (6 lines) in frontend/src/features/tasks/state/TaskStateMa…
info Commented-code block (5 lines) in frontend/src/features/tasks/components/input/…

View all commented-out code findings →

Config drift 24 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

medium [AUC009] Sensitive function route lacks elevated authorization evidence: A rout… frontend/src/app/runtime-config/route.ts:30
high [MINED108] `self._get_knowledge_base` used but never assigned in __init__: Meth…
low Possibly dead Python function: configure_model chat_shell/chat_shell/agents/graph_builder.py:848
low File has no detected symbols: frontend/playwright.config.ts
low File has no detected symbols: frontend/tailwind.config.js
low File has no detected symbols: frontend/next.config.js
low File has no detected symbols: frontend/jest.config.ts
low File has no detected symbols: frontend/postcss.config.js
low File has no detected symbols: frontend/src/__tests__/config/next-config-perform…
low File has no detected symbols: frontend/src/__tests__/app/runtime-config-cache.t…
low File has no detected symbols: frontend/src/__tests__/features/settings/utils/mc…
low File has no detected symbols: frontend/src/__tests__/features/settings/utils/em…

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/7b2123d8-a9f1-4c2e-9d75-6c93ecc32986/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7b2123d8-a9f1-4c2e-9d75-6c93ecc32986/

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.