Is Qwen Audio Agent safe to use?

Qwen Audio Agent has an HVTrust score of 86.0/100 (Grade A), ranked #71 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Qwen Audio Agent?

Qwen Audio Agent scores 86.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.8k GitHub stars and is categorized under Voice & Conversational.

Qwen Audio Agent

Repository Website

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

Voice & Conversational JavaScript Listed Apache-2.0

Is Qwen Audio Agent safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.5 / 10

Provenance Attested

Signed commits 91%

Last push 3d ago

Advisories None known

Compare Qwen Audio Agent

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

Pick any agent to compare →

Suggest a correction

In detail: Qwen Audio Agent scores 86.0/100 (Grade A), ranked #71 of 1343 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; 91% of recent commits are signed; no published advisory affects its latest release (qwen-audio-agent); last pushed 2026-09-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How Qwen Audio Agent could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.5 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Maintained 0 +5.1 → 91.1 A · #2 of 13

Already done? Suggest a correction Add the trust badge

How Qwen Audio Agent compares in Voice & Conversational

Bars show each HVTrust score; the tick marks Qwen Audio Agent’s 86.0.

Where the 86.0 comes from

HVTrust dimensions vs the Voice & Conversational average

86.0 / 100 · 100.0% confidence

Qwen Audio Agent Voice & Conversational average (13 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.9 / 25

8.5 above avg 10.4

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.5 above avg 12.5

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

0.6 above avg 12.6

Maintenance60% last-push freshness · 40% commit activity

19.8 / 20

3.7 above avg 16.1

AdoptionLog-scaled stars · package downloads

11.5 / 20

0.7 above avg 10.8

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.

Compare with LiveKit Agents Get email alerts for Qwen Audio Agent View Voice & Conversational Report missing data

81.8

Activity sub-score · out of 100

In Voice & Conversational

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 →

Rank Trend

2026-09-29 2026-09-30

Activity & Reach

Stars

2.8k

Forks

280

Last Push

2026-09-28

3 days ago

Commits (4 wk)

252

Downloads (7d)

247

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #69

Analysis

Activity Inputs

81.8 / 100

StarsRepository reach

20.7 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Sep 30, 2026

Signed Commits

91%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

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

Common questions about Qwen Audio Agent

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 3 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?

91% 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

Qwen Audio Agent vs LiveKit Agents → Qwen Audio Agent vs Pipecat → Qwen Audio Agent vs AstrBot →

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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 536 spots (#598 → #62)

2026-09-23

HVTrust Changed

HVTrust up 52.4pts (33.9 → 86.3)

2026-09-22

Newly Listed

First tracked at rank #598

2026-09-21

Removed From Active Tracking

Removed from active tracking

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

GitHub → Website → npm: qwen-audio-agent

Embed Badge Badge guide for maintainers →

For maintainers

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.4 · Raw JSON