Item detail
github.com

stainlu/hermes-labyrinth

stainlu/hermes-labyrinth is a observability plugin in RepoRadar's Evaluation and Observability section, holding Silver tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 8.9 out of 10.

Score7.8
Popularity1.0
Risknone
TierSilver
Score breakdown
Usefulness8.0
Novelty7.0
Momentum5.0
Maturity5.7
Open-source/build8.4
Evidence8.0
Workflow potential8.9
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for Hermes users who want a clearer post-run view of what an autonomous agent actually did without adding a hosted telemetry service or a write-capable control layer.

Who should use it

Hermes users debugging autonomous runsOperators who need a clearer view of cron and subagent behaviorDevelopers reviewing tool-call traces and failure pointsTeams that want read-only observability before adopting heavier tracing

Who should skip it

Skip stainlu/hermes-labyrinth if the source link, documentation, or setup requirements do not align with your current workflow or stack.

About this signal

stainlu/hermes-labyrinth is tracked by RepoRadar as a observability plugin in the Evaluation and Observability section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. stainlu/hermes-labyrinth leads on workflow potential (8.9) and open-source/build quality (8.4); its lowest signal is momentum (5.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 stainlu/hermes-labyrinth a composite score of 7.8 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 'none' 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

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links
Closest alternatives / related signals
hermes-agentobservabilitydashboardcronpluginmit