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

Scan timing: clone 3.68s · analysis 17.0s · 8.0 MB · GitHub preflight 454ms

browser-use/browser-use

https://github.com/browser-use/browser-use · scanned 2026-06-05 06:49 UTC (6 days, 1 hour ago) · 10 languages

549 raw signals (273 security + 276 graph) 54th percentile · Python · medium (20-100K LoC)

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

Complete repo analysis

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

JSON
Combined
59.5
/100
Security checks
54
104 findings
System graph
65
100.0% cov · 101 findings
Critical
4
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 35.5 0.25 8.88
testing_score 100.0 0.20 20.00
documentation_score 85.0 0.15 12.75
practices_score 89.0 0.15 13.35
code_quality 24.5 0.10 2.46
Overall 1.00 66.4
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 4 High 25 Medium 19 Low 74 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 104 System graph 101 Crowd 0 Layer: Quality 121 Security 13 Cicd 8 Software 52 Network 1 Hardware 8 Frontend 1 Api 1

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

#1
Possible secret in browser_use/config.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 browser_use/config.py:306; move to env var / secrets manager.
browser_use/config.py:306
#2
Possible secret in browser_use/telemetry/service.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 browser_use/telemetry/service.py:32; move to env var / secrets manager.
browser_use/telemetry/service.py:32
#3
Insecure pattern 'eval_used' in browser_use/skill_cli/python_session.py:82
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
browser_use/skill_cli/python_session.py:82
#4
Insecure pattern 'exec_used' in browser_use/skill_cli/python_session.py:88
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
browser_use/skill_cli/python_session.py:88
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/test.yaml:177
#6
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/test.yaml:247
#7
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/test.yaml
#8
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:33
#9
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:36
#10
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:39

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/54316748-e993-41aa-8fc3-f9d476bab5d1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/54316748-e993-41aa-8fc3-f9d476bab5d1/

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.