Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for self-hosters and agent builders who need a real execution service, not just a demo notebook, when tool-using agents have to run code and return artifacts.
Who should use it
Who should skip it
Skip ClickHouse/code-interpreter for now if your priority is a tool you can use today without configuring a build pipeline or development environment.
About this signal
ClickHouse/code-interpreter is tracked by RepoRadar as a sandbox backend in the AI Infrastructure section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Silver tier and hard setup difficulty. ClickHouse/code-interpreter leads on workflow potential (9.0) 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 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 ClickHouse/code-interpreter a composite score of 7.9 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 'conditional' 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
Runs arbitrary user-submitted code inside sandboxes, so first evaluation should stay on isolated infrastructure with tight resource limits; README notes some session-management routes remain unauthenticated for backwards compatibility, so production deployments need an auth review before exposure.