Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want real browser automation for agents without locking themselves to a single desktop app or vendor-specific computer-use layer.
Who should use it
Who should skip it
Move on from iFurySt/open-browser-use if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
iFurySt/open-browser-use is tracked by RepoRadar as a browser automation in the Developer Tools section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. iFurySt/open-browser-use leads on workflow potential (9.4) and open-source/build quality (8.4); its lowest signal is maturity (5.8), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned iFurySt/open-browser-use a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Any agent that can drive a real browser can interact with logged-in tabs and live sessions, so test it with disposable accounts or a dedicated browser profile first; The project exposes automation and CDP control across multiple SDKs, which is powerful but easy to over-scope unless you define clear page and account boundaries up front.