Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for evaluators comparing model providers' reasoning-trace redaction quality, developers picking a reasoning provider for a consumer product, and AI safety researchers tracking reasoning-trace leakage at the API layer.
Who should use it
Who should skip it
Skip lyramakesmusic/neuralese-leaker if you cannot isolate its execution environment or audit what data it touches before connecting anything sensitive.
About this signal
lyramakesmusic/neuralese-leaker is tracked by RepoRadar as a hosted app or demo in the Reasoning Trace Security section. First seen 2026-08-12; the source record was last checked on 2026-08-12. The current verdict is 'research only' with a Silver tier and easy setup difficulty. The standout signals for lyramakesmusic/neuralese-leaker are novelty (10.0) and workflow potential (8.8), while maturity (6.1) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The lyramakesmusic/neuralese-leaker record combines a 8.4/10 composite score with separate popularity (0.7), risk (medium), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It is a consumer-side tool that exposes reasoning traces; deploy only in controlled evaluation environments with the provider's prior authorization; It depends on the OpenRouter API; treat the model selection as a research-only variable, not a production decision.