Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers and teams who want agent-friendly task tracking that is more structured than a chat thread but lighter than Jira, GitHub Issues, or a full hosted project-management stack.
Who should use it
Who should skip it
Move on from kenn-io/kata if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
kenn-io/kata is tracked by RepoRadar as a developer tool in the Developer Tools section. It was first seen on 2026-06-27 and last updated on 2026-06-27. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for kenn-io/kata are workflow potential (10.0) and practical usefulness (9.0), while setup ease (6.4) 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 kenn-io/kata 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 44.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
The optional --with-agents setup edits local agent guidance files, so inspect the managed briefing before using it in an established workflow; The remote daemon and federation path add another state surface beyond the local SQLite ledger, so start local-first before sharing across machines; The project is still pre-1.0, so command contracts and UI details can shift as the maintainer hardens the workflow.