Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Mac users who want a more durable multi-agent workspace than a pile of terminal tabs, while keeping the working context local and inspectable.
Who should use it
Who should skip it
Move on from chenzl25/lantor if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
chenzl25/lantor is tracked by RepoRadar as a ai product in the Desktop Agents section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, chenzl25/lantor is strongest on workflow potential (9.4) and open-source/build quality (8.4) and weakest on maturity (5.8) — a profile worth weighing against your own priorities. 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 chenzl25/lantor 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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It manages local attachments, chat history, and agent workspaces, so first evaluation should stay on non-sensitive projects until the local data model and backup flow are understood; The current positioning is Mac-first, which limits cross-platform fit for teams that need the same workspace experience on Windows or Linux today.