Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want to put agent loops, tool use, resumable streams, and browser-hosted workspaces directly inside a web app without standing up a custom model backend on day one.
Who should use it
Who should skip it
Move on from davideast/inbrowser-agent if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
davideast/inbrowser-agent is tracked by RepoRadar as a browser ai stack in the AI Infrastructure section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. davideast/inbrowser-agent leads on workflow potential (9.7) and novelty (9.0); its lowest signal is momentum (6.0), 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 davideast/inbrowser-agent a composite score of 8.6 out of 10, placing it in the Gold 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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The workspace and sandbox packages can run shell commands, installs, and git inside a browser-hosted workspace, so first evaluation should stay on throwaway projects and explicit tool allowlists; Cloud-provider mode is BYOK in the client, so review how your app stores and revokes user-supplied API keys before shipping it to end users.