Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders and engineering teams who already like coding agents but need durable project state, explicit verification, and a cleaner way to resume serious delivery work after compaction or interrupted sessions.
Who should use it
Who should skip it
Consider valkor-ai/loom lower priority if you already have a working solution in this category.
About this signal
valkor-ai/loom is tracked by RepoRadar as a delivery harness in the Coding Workflows section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, valkor-ai/loom is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — 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 valkor-ai/loom a composite score of 8.6 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 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
It writes local adapter files and project delivery state under ~/.loom and .loom so the first evaluation should stay on a test repository where those changes can be inspected; Loom can drive verification and deployment-style loops through your existing coding-agent CLI so keep the first run off production systems until the repair and handoff flow is understood.