Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Hermes users who want browser context inside their agent loop without jumping straight to invasive automation or cookie-grabbing extensions.
Who should use it
Who should skip it
Consider abundantbeing/hermes-browser-extension lower priority if you already have a working solution in this category.
About this signal
abundantbeing/hermes-browser-extension is tracked by RepoRadar as a browser extension in the Developer Tools section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. abundantbeing/hermes-browser-extension leads on workflow potential (9.4) and open-source/build quality (8.4); 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 abundantbeing/hermes-browser-extension 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 61.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 page context you refresh into the side panel becomes available to the connected Hermes runtime for the duration of the session; Remote API-server mode widens the trust boundary beyond localhost, so keep it to a trusted host with a strong API key and CORS allowlist; It is intentionally read-only in v0.1, so treat it as context capture rather than browser automation when planning workflows.