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
105 of your 279 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 7.18s · analysis 12.51s · 14.8 MB · GitHub preflight 438ms

zhouyoukang1234-spec/windsurf-assistant

https://github.com/zhouyoukang1234-spec/windsurf-assistant · scanned 2026-06-05 15:26 UTC (5 days, 1 hour ago) · 10 languages

745 raw signals (249 security + 496 graph) 0th percentile · Javascript · medium (20-100K LoC) System graph score 55 (lower by 16)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 1 hour ago · v2 · 294 actionable findings from 2 signal sources. 203 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
47.2
/100
Security checks
39
72 findings
System graph
55
100.0% cov · 222 findings
Critical
7
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 38.0 0.25 9.50
testing_score 23.0 0.20 4.60
documentation_score 60.4 0.15 9.06
practices_score 65.0 0.15 9.75
code_quality 4.0 0.10 0.40
Overall 1.00 39.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 7 High 26 Medium 21 Low 180 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 72 System graph 222 Crowd 0 Layer: Quality 102 Security 26 Software 54 Cicd 2 Frontend 99 Api 11

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

#1
Possible secret in Windsurf万法归宗/060-修复_Repair/agent-remote-repair-main/remote-agent/inject_login.py
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 Windsurf万法归宗/060-修复_Repair/agent-remote-repair-main/remote-agent/inject_login.py:12; move to env var / secrets manager.
Windsurf万法归宗/060-修复_Repair/agent-remote-repair-main/remote-agent/inject_login.py:12
#2
Insecure pattern 'exec_used' in n.js:7
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
n.js:7
#3
Insecure pattern 'exec_used' in Windsurf万法归宗/070-插件_Plugins/020-道VSIX_DaoAgi/dao-proxy-min/extension.js:1150
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
Windsurf万法归宗/070-插件_Plugins/020-道VSIX_DaoAgi/dao-proxy-min/extension.js:1150
#4
Insecure pattern 'exec_used' in Windsurf万法归宗/070-插件_Plugins/020-道VSIX_DaoAgi/dao-proxy-min/package.json:100
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
Windsurf万法归宗/070-插件_Plugins/020-道VSIX_DaoAgi/dao-proxy-min/package.json:100
#5
Insecure pattern 'exec_used' in 130-道独立体_Standalone/01-VM/vm-side/dao_nano_public.js:14
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
130-道独立体_Standalone/01-VM/vm-side/dao_nano_public.js:14
#6
Insecure pattern 'exec_used' in packages/dao-proxy-min/extension.js:1183
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/dao-proxy-min/extension.js:1183
#7
Insecure pattern 'exec_used' in packages/dao-proxy-min/package.json:101
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/dao-proxy-min/package.json:101
#8
Dangling fetch: GET /_devin-auth/password/login (_archive/wam-v17.42.20/extension.js:5110)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#9
Dangling fetch: GET /api/notify-test (packages/wam/dao_stuck.js:2270)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#10
Dangling fetch: GET http://127.0.0.1:${s.port}/health (web/dao_app.js:1116)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.

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/f833405c-b5d5-423e-926f-75cc8b93ff75/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f833405c-b5d5-423e-926f-75cc8b93ff75/

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.