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

Scan timing: clone 2.57s · analysis 21.15s · 9.8 MB · GitHub API rate-limit (preflight)

clawvisor/clawvisor

https://github.com/clawvisor/clawvisor · scanned 2026-06-05 17:43 UTC (4 days, 21 hours ago) · 10 languages

626 raw signals (386 security + 240 graph) 9th percentile · Go · large (100-500K LoC) System graph score 65 (lower by 4)

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

Complete repo analysis

Last scanned 4 days, 21 hours ago · v2 · 216 actionable findings from 2 signal sources. 290 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
57.1
/100
Security checks
49
134 findings
System graph
65
100.0% cov · 82 findings
Critical
9
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 3.0 0.25 0.75
testing_score 80.0 0.20 16.00
documentation_score 100.0 0.15 15.00
practices_score 77.0 0.15 11.55
code_quality 41.4 0.10 4.14
Overall 1.00 60.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 9 High 83 Medium 25 Low 54 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 134 System graph 82 Crowd 0 Layer: Software 90 Cicd 14 Security 18 Quality 69 Api 1 Frontend 9 Network 2 Hardware 13

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

#1
Possible secret in security/zap/automation.yaml
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 security/zap/automation.yaml:10; move to env var / secrets manager.
security/zap/automation.yaml:10
#2
Possible secret in security/zap/run-scan.sh
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 security/zap/run-scan.sh:29; move to env var / secrets manager.
security/zap/run-scan.sh:29
#3
Possible secret in internal/clawvisorcli/cmd_tui.go
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 internal/clawvisorcli/cmd_tui.go:107; move to env var / secrets manager.
internal/clawvisorcli/cmd_tui.go:107
#4
Insecure pattern 'eval_used' in internal/runtime/llmproxy/postprocess.go:1919
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
internal/runtime/llmproxy/postprocess.go:1919
#5
Insecure pattern 'eval_used' in internal/runtime/conversation/anthropic_response.go:77
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
internal/runtime/conversation/anthropic_response.go:77
#6
Insecure pattern 'eval_used' in internal/runtime/conversation/openai_response.go:132
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
internal/runtime/conversation/openai_response.go:132
#7
Dockerfile pipes a remote installer into a shell
GapSeverity.HIGH Layer.HARDWARE score 0.375
Why: high severity
e2e/install/Dockerfile:39
#8
`dangerouslySetInnerHTML` used in a React component — web/src/components/ServiceIcon.tsx:38
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#9
Privileged port 12 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in internal/e2e/scenario/library/session_authorize.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
internal/e2e/scenario/library/session_authorize.yaml
#10
Privileged port 30 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in internal/e2e/scenario/library/session_authorize.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
internal/e2e/scenario/library/session_authorize.yaml

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/32c90083-0b1f-4275-ac0e-ee264df3298f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/32c90083-0b1f-4275-ac0e-ee264df3298f/

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.