Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want better evidence, traceability, and rollback paths when Claude Code, Codex, or similar agents are working in real repositories.
Where this stands now
h5i-dev/h5i ranks #137 of 3231 tracked Radar items by composite score (8.5 against a section median of 4.9). The section currently carries 2115 Bronze, 645 Gold, 471 Silver. RepoRadar has retained observations for this record since 2026-06-20 (112 days in the current window). Signal extremes versus the section: momentum at the 76th percentile; novelty at the 85th percentile.
Who should use it
Who should skip it
Consider h5i-dev/h5i lower priority if you already have a working solution in this category.
About this signal
h5i-dev/h5i is tracked by RepoRadar as an agent project in the Radar section. First seen 2026-06-20; the source record was last checked on 2026-06-20. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for h5i-dev/h5i are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The h5i-dev/h5i record combines a 8.5/10 composite score with separate popularity (20.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
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 operates inside active repositories and records prompts, commands, and logs, so teams should scope what gets captured and keep sensitive projects behind tighter review.