Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Hermes operators who want to inspect agent state, drift, and spend without spelunking through databases, logs, and config files by hand.
Who should use it
Who should skip it
Move on from joeynyc/hermes-hudui if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
joeynyc/hermes-hudui is tracked by RepoRadar as a agent dashboard 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. joeynyc/hermes-hudui leads on workflow potential (9.8) and practical usefulness (9.0); its lowest signal is setup ease (6.4), 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 joeynyc/hermes-hudui a composite score of 8.7 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
It reads real local Hermes memory, session, and governance data, so first rollout should stay on machines where that agent state is already trusted; The dashboard exposes operational actions such as updates and plugin management, so teams should review the control surface before putting it on shared operator boxes.