RepoRadar surfaced browser-use/browser-use — a developer tool — into the AI Automation section, where it sits at Silver tier with a 'watch' verdict. Its strongest signal is workflow potential, scored 8.8 out of 10.
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Practical teams should care when web automation is becoming part of customer-visible assistants or internal RPA workflows.
Who should use it
browser automation buildersworkflow/agent engineersteams testing AI-assisted web tasks
Who should skip it
Skip browser-use/browser-use unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
browser-use/browser-use is tracked by RepoRadar as a developer tool in the AI Automation section. First seen 2026-06-18; the source record was last checked on 2026-06-18. The current verdict is 'watch' with a Silver tier and intermediate setup difficulty. browser-use/browser-use leads on workflow potential (8.8) and open-source/build quality (8.4); its lowest signal is setup ease (6.2), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The browser-use/browser-use record combines a 8.0/10 composite score with separate popularity (71.0), risk (conditional), and setup (intermediate) signals. See the scoring methodology for the current weights and evidence definitions.
Hands-on setup or capability check retained by RepoRadar verification harness. Last checked 2026-07-13T03:23:08.661423Z.
partial · cohort-20260712-browser-use-import
Tester
RepoRadar automated local verification harness
Started
2026-07-13T03:23:05.494892Z
Completed
2026-07-13T03:23:08.661423Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
0 minute(s)
Evidence scope
Bounded setup or capability check
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
Executed bounded check: Install and import browser-use in an isolated Python environment.
Captured the complete sanitized stdout, stderr, exit status, and 3.17-second wall time.
Observed results
Command exited 0 after 3.17 seconds.
Expected marker 'CHECK_OK' was observed in retained output.
Observed strengths
browser-use==0.13.4 installed and imported successfully in the isolated Python environment without launching a browser or agent.
Friction
The command emitted stderr; warnings or errors are preserved in the retained log for review.
Limitations
No browser binary, website, agent, provider credential, or model call was used.
This bounded cohort check is not a production benchmark or a claim of real user-workflow adoption.
Pricing assessment: No paid plan or metered provider usage was exercised; package or licensing, hosting, and provider costs remain workflow-dependent.
Privacy assessment: No repository content, user data, or provider prompt was transmitted; broader product data handling was not assessed by this bounded run.
47 dated snapshots retained from 2026-06-18 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.
RepoRadar score8.0 current · +0.0 netRepository momentum10.0 current · +3.0 netGitHub stars (observed)109,111 current · +4,603 net