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.
Sign up free Scan another repo
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)

wecode-ai/Wegent

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
Combined
71.9
/100
Security checks
82
160 findings
System graph
62
100.0% cov · 636 findings
Critical
8
click to filter
Agents
6
0 votes
Crowd
0
reported
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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in frontend/src/i18n/locales/en/common.json
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in frontend/src/i18n/locales/en/common.json:920; move to env var / secrets manager.
frontend/src/i18n/locales/en/common.json:920
#2
Possible secret in frontend/src/features/settings/components/GitHubEdit.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in frontend/src/features/settings/components/GitHubEdit.tsx:393; move to env var / secrets manager.
frontend/src/features/settings/components/GitHubEdit.tsx:393
#3
Possible secret in frontend/src/features/login/components/LoginForm.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in frontend/src/features/login/components/LoginForm.tsx:27; move to env var / secrets manager.
frontend/src/features/login/components/LoginForm.tsx:27
#4
Possible secret in frontend/e2e/utils/auth.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in frontend/e2e/utils/auth.ts:8; move to env var / secrets manager.
frontend/e2e/utils/auth.ts:8
#5
Possible secret in frontend/e2e/utils/auth-state.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in frontend/e2e/utils/auth-state.ts:3; move to env var / secrets manager.
frontend/e2e/utils/auth-state.ts:3
#6
Possible secret in docker/device/Dockerfile
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in docker/device/Dockerfile:159; move to env var / secrets manager.
docker/device/Dockerfile:159
#7
Possible secret in wework/src/pages/LoginPage.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in wework/src/pages/LoginPage.tsx:35; move to env var / secrets manager.
wework/src/pages/LoginPage.tsx:35
#8
FastAPI POST `query_documents` without auth dependency — knowledge_runtime/knowledge_runtime/api/endpoints/query.py:19
GapSeverity.HIGH Layer.SECURITY score 0.537
Why: high severity · OWASP-class risk
Fix: Add `user = Depends(get_current_user)` to the function signature in knowledge_runtime/knowledge_runtime/api/endpoints/query.py:19.
knowledge_runtime/knowledge_runtime/api/endpoints/query.py:19
#9
FastAPI POST `delete_document_index` without auth dependency — knowledge_runtime/knowledge_runtime/api/endpoints/admin.py:27
GapSeverity.HIGH Layer.SECURITY score 0.537
Why: high severity · OWASP-class risk
Fix: Add `user = Depends(get_current_user)` to the function signature in knowledge_runtime/knowledge_runtime/api/endpoints/admin.py:27.
knowledge_runtime/knowledge_runtime/api/endpoints/admin.py:27
#10
FastAPI POST `purge_knowledge_index` without auth dependency — knowledge_runtime/knowledge_runtime/api/endpoints/admin.py:37
GapSeverity.HIGH Layer.SECURITY score 0.537
Why: high severity · OWASP-class risk
Fix: Add `user = Depends(get_current_user)` to the function signature in knowledge_runtime/knowledge_runtime/api/endpoints/admin.py:37.
knowledge_runtime/knowledge_runtime/api/endpoints/admin.py:37

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.