Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for security-minded teams that want to instrument agent tool use centrally instead of trusting each local harness to make safe decisions on its own.
Who should use it
Who should skip it
Pass on kontext-security/kontext-cli if you need something non-technical and turnkey rather than a tool that requires comfort with CLI, dependencies, or system configuration.
About this signal
kontext-security/kontext-cli is tracked by RepoRadar as a infrastructure tool in the AI Security section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'worth watch' with a Silver tier and hard setup difficulty. The standout signals for kontext-security/kontext-cli are open-source/build quality (8.4) and workflow potential (8.1), while momentum (4.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 kontext-security/kontext-cli a composite score of 7.7 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 2.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 sits directly on the allow or deny path for real tool actions, so a bad rule or rollout mistake can block useful work or miss a dangerous action; Setup installs a user-level daemon and stores a workspace token locally, which raises credential and endpoint handling requirements from day one; The self-serve setup path is currently macOS-focused, so cross-platform teams need to verify the operational story before standardizing on it.