Qwen Audio Agent vs Rasa
Qwen Audio Agent leads on trust: 86.0/100 (Grade A) against 59.3/100 (Grade C), a 26.7-point gap. Qwen Audio Agent leads on maintenance and supply-chain integrity; Rasa leads on adoption and rests on broader evidence. Note: Qwen Audio Agent's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.
A realtime voice runtime that keeps Agents talking, working, and present. Real-time Voice Runtime for AI Agents
Choose Qwen Audio Agent if maintenance and supply-chain integrity matter most.
- +12.4Maintenance: last push 3d ago, against 69d ago
- +9.5Safety / Integrity: 91% of recent commits signed, against 59%
- +7.2Identity / Provenance: package provenance attested, against none
💬 Open source machine learning framework to automate text- and voice-based conversations: NLU, dialogue management, connect to Slack, Facebook, and more - Create chatbots and voice assistants
Choose Rasa if adoption matters most.
- +5.2Adoption: 53.7k weekly downloads against 247
- A vs BEvidence coverage: 4 of 5 independent signal types, against 3
Where they differ
An independent, evidence-based trust comparison of Qwen Audio Agent and Rasa, two Voice & Conversational projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | Qwen Audio AgentQwenAudio/qwen-audio-agent | RasaRasaHQ/rasa |
|---|---|---|
| HVTrust score | 86.0 | 59.3 |
| Evidence grade | A | C |
| Coverage grade | B | A |
| Overall rank | #71 | #653 |
| Rank in Voice & Conversational | #2 | #6 |
| GitHub stars | 2.8k | 21.3k |
| Last updated | 3d ago | 69d ago |
| Build provenance | Yes | No |
| OSSF Scorecard | 5.5 / 10 | 5.2 / 10 |
| License | Apache-2.0 | Apache-2.0 |
| Downloads | 247/wk | 54k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 18.9 | 9.4 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 13.2 | 12.9 |
| Maintenance / 20 | 19.8 | 7.4 |
| Adoption / 20 | 11.5 | 16.7 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | — |
| External providers | — | 3 — Amazon Bedrock, Postgres, Redis |
| Requires API keys | Yes | No |
| Plugin surface | — | plugins |
| Provenance drift | Match | Match |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →