Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that want coding agents to inspect blast radius, architecture, and verification evidence before they start rewriting code.
Where this stands now
Cranot/roam-code ranks #15 of 64 tracked Developer Workflow items by composite score (8.3 against a section median of 8.1). The section currently carries 32 Gold, 30 Silver, 2 Bronze. RepoRadar has retained observations for this record since 2026-06-20 (97 days in the current window). Signal extremes versus the section: momentum at the 15th percentile.
Who should use it
Who should skip it
Skip Cranot/roam-code if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
Cranot/roam-code is tracked by RepoRadar as a developer tool in the Developer Workflow 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. Cranot/roam-code leads on workflow potential (9.8) 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 Cranot/roam-code record combines a 8.3/10 composite score with separate popularity (24.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
The index can contain proprietary source code, architecture details, and historical evidence about changes, so keep the local database and any connected agent session inside your normal repo trust boundary; The optional metrics push surface is opt-in rather than default, but verify outbound settings before using it on sensitive codebases.