Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for local-AI users and Mac builders who want system-wide autocomplete from their own on-device model instead of a browser tab or editor-only assistant.
Who should use it
Who should skip it
Pass on johnbean393/KeyType if its scope or audience does not match what your team is building right now.
About this signal
johnbean393/KeyType is tracked by RepoRadar as a local ai desktop in the Local AI section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, johnbean393/KeyType is strongest on workflow potential (9.5) and open-source/build quality (8.4) 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 johnbean393/KeyType a composite score of 8.4 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 reads the focused text field through macOS accessibility APIs, so test it on a non-sensitive machine or exclude apps that may surface credentials, private notes, or regulated data; Completion quality depends on the local model you load and the typing context you expose, so validate latency and false-completion behavior before using it in production writing workflows.