Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want a concrete control boundary for agent actions instead of relying on prompt-only guardrails.
Where this stands now
Mindburn-Labs/helm-ai-kernel ranks #315 of 2770 tracked Radar items by composite score (8.3 against a section median of 4.9). The section currently carries 1659 Bronze, 645 Gold, 466 Silver. RepoRadar has retained observations for this record since 2026-06-19 (106 days in the current window). Signal extremes versus the section: novelty at the 83th percentile.
Who should use it
Who should skip it
Pass on Mindburn-Labs/helm-ai-kernel if its scope or audience does not match what your team is building right now.
About this signal
Mindburn-Labs/helm-ai-kernel is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Mindburn-Labs/helm-ai-kernel leads on workflow potential (9.8) 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 public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The Mindburn-Labs/helm-ai-kernel record combines a 8.3/10 composite score with separate popularity (62.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
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
HELM AI Kernel sits directly in the execution path for tools and model requests, so validate policy behavior and receipt verification on non-critical workflows before trusting it as a production control boundary.