Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for voice-agent developers, AI app developers, real-time audio developers, AI-curious readers tracking open-source voice agent releases, AI robot developers (the canonical production deployment is the Reachy Mini robot conversation backend), and any developer wiring an AI coding agent to a local voice agent stack -- and who can pair huggingface/speech-to-speech with a HuggingFace open-weigh
Who should use it
Who should skip it
Skip huggingface/speech-to-speech if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
huggingface/speech-to-speech is tracked by RepoRadar as a apache-2.0 official huggingface in the HuggingFace Local Voice Agent Library (OpenAI-Re section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, huggingface/speech-to-speech is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on maturity (6.8) — 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 huggingface/speech-to-speech a composite score of 8.7 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 'low' 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 5; 558* repo is at active maintenance but the consumer SHOULD review the voice cloning capability (the Qwen3-TTS VoiceDesign family supports voice cloning -- the consumer SHOULD review the consumer's target use case against the model's documentation before relying on voice cloning; particularly for impersonation or deceptive use cases); the consumer SHOULD benchmark the consumer's local STT + LLM + TTS stack on the consumer's target hardware before relying on the pipeline in production.