Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who have outgrown local demos and need a real execution layer for isolated tools, generated code, and background agent jobs.
Who should use it
Who should skip it
Skip tensorlakeai/tensorlake if you cannot isolate its execution environment or audit what data it touches before connecting anything sensitive.
About this signal
tensorlakeai/tensorlake is tracked by RepoRadar as an AI project in the Radar section. It was first seen on 2026-06-19 and last updated on 2026-06-19. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. The standout signals for tensorlakeai/tensorlake are workflow potential (9.9) and practical usefulness (9.0), while setup ease (4.2) 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. 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 tensorlakeai/tensorlake a composite score of 8.8 out of 10, placing it in the Gold 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 79.0 and never affects the composite score or tier. The risk label of 'medium' 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
This runtime is designed for executing tools and model-generated code inside remote sandboxes, so treat it as production infrastructure and keep credentials, network access, and blast radius tightly scoped during any early rollout.