Qwen Audio Agent

A realtime voice runtime that keeps Agents talking, working, and present. Real-time Voice Runtime for AI Agents

Voice & Conversational JavaScript Grade A Listed Apache-2.0
85.1/100
Rank #56 of 1320
Compare Qwen Audio Agent

How does it stack up against its Voice & Conversational neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Mcp Status Changed +2

Is Qwen Audio Agent safe? Qwen Audio Agent scores 85.1/100 (Grade A), ranked #56 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 69% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Voice & Conversational

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-03
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-03
Rank Moved
Rank rose 18 spots (#70 → #52)
2026-08-31
Rank Moved
Rank dropped 10 spots (#66 → #76)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
80.9
Activity sub-score · out of 100
#3

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 22:32 UTC · Repo last pushed today

Rank Trend

2026-08-16 2026-09-04

Activity & Reach

Stars
2.3k
Forks
203
Last Push
2026-09-04
today
Commits (4 wk)
380
Downloads (7d)
209
npm
HN mentions (30d)
Open Issues
10
Rank Change
▼4
was #52

Analysis

HVTrust Dimensions vs Voice & Conversational

85.1 / 100 · 100.0% confidence

Qwen Audio Agent Voice & Conversational average (12 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.8 / 25
7.4 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.4 above avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
0.9 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
3.5 above avg 16.5
AdoptionLog-scaled stars · package downloads
11.2 / 20
in line with avg 10.8

Activity Inputs

80.9 / 100
StarsRepository reach
20.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.7 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
5.5 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
69%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 10
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 10
Vulnerabilities 0

Is Qwen Audio Agent safe?

Public supply-chain signals for Qwen Audio Agent are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Qwen Audio Agent carries less obvious unverified-evidence risk than projects with thin signals.
Does Qwen Audio Agent publish package provenance?
Yes. Qwen Audio Agent's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Qwen Audio Agent have an OpenSSF Scorecard?
Qwen Audio Agent has an OpenSSF Scorecard score of 5.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Qwen Audio Agent actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Qwen Audio Agent use?
Qwen Audio Agent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Qwen Audio Agent's commits signed?
69% of the last 100 commits to Qwen Audio Agent are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Qwen Audio Agent head-to-head

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Qwen Audio Agent appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Qwen Audio Agent's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-03
Mcp Status Changed
Detected MCP server support changed: declared → implemented

Maintain Qwen Audio Agent?

For maintainers

HVTrust scores Qwen Audio Agent from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 5Listed 1HVTrust 1Grade 1Scorecard 1MCP 1
2026-09-03
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-09-03
Rank Moved
Rank rose 18 spots (#70 → #52)
2026-08-31
Rank Moved
Rank dropped 10 spots (#66 → #76)
2026-08-27
Scorecard Added
OSSF Scorecard: 5.5/10
2026-08-27
Grade Changed
Trust grade B → A
2026-08-27
Rank Moved
Rank rose 80 spots (#147 → #67)
2026-08-27
HVTrust Changed
HVTrust up 11.5pts (71.4 → 82.9)
2026-08-26
Rank Moved
Rank dropped 16 spots (#131 → #147)
2026-08-17
Rank Moved
Rank rose 12 spots (#133 → #121)
2026-08-16
Newly Listed
First tracked at rank #133

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 85.1 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/qwen-audio-agent.svg)](https://hvtracker.net/agents/qwen-audio-agent)
HTML:
<a href="https://hvtracker.net/agents/qwen-audio-agent"><img src="https://hvtracker.net/badge/qwen-audio-agent.svg" alt="HVTrust"></a>

Other agents in Voice & Conversational

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON