Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that are moving agents closer to real data and real actions and want something more concrete than vague 'guardrails' talk.
Where this stands now
jnMetaCode/shellward ranks #310 of 3231 tracked Radar items by composite score (8.3 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 70th percentile; novelty at the 85th percentile.
Who should use it
Who should skip it
Move on from jnMetaCode/shellward if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
jnMetaCode/shellward is tracked by RepoRadar as a developer tool 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 Silver tier and advanced setup difficulty. jnMetaCode/shellward leads on workflow potential (9.4) and open-source/build quality (8.4); its lowest signal is setup ease (4.2), 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 jnMetaCode/shellward record combines a 8.3/10 composite score with separate popularity (10.0), risk (conditional), and setup (advanced) 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It sits inline on prompts, tool calls, and potentially sensitive data, so deployment location, logging, and policy tuning matter as much as the default rules.