Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for coding-agent power users who want session-to-session recall with less manual upkeep, but the project is still early and its transcript-processing hooks deserve a careful pilot first.
Who should use it
Who should skip it
Hold off on kurikomi-labs/komi-learn until it graduates from watchlist status with stronger evidence.
About this signal
kurikomi-labs/komi-learn is tracked by RepoRadar as a agent memory layer in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. The standout signals for kurikomi-labs/komi-learn are workflow potential (8.6) and open-source/build quality (8.4), while momentum (5.0) trails — that balance shapes where it fits best. 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 kurikomi-labs/komi-learn a composite score of 7.8 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 31.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
The distill step reads session transcripts and may send derived context through a model provider, so review what project information can leave your machine before enabling it on sensitive repos; The optional community pool publishes approved learnings through GitHub review flows, so keep sharing disabled until you verify the scrub and approval path fits your environment.