Is Qwen MM Plugins safe to use?

Qwen MM Plugins has an HVTrust score of 59.4/100 (Grade C), ranked #109 of 359 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Qwen MM Plugins?

Qwen MM Plugins scores 59.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.1k GitHub stars and is categorized under Agent Skills.

Qwen MM Plugins

Repository by QwenLM

Make any agent harness multimodal-native.

Agent Skills Python Listed Apache-2.0

Is Qwen MM Plugins safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.9 / 10

Provenance None

Signed commits 21%

Last push 8d ago

Compare Qwen MM Plugins

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Qwen MM Plugins scores 59.4/100 (Grade C), ranked #109 of 359 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.9/10; 21% of recent commits are signed; last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Qwen MM Plugins 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 4.9 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +8.5 → 67.9 B · #42 of 359
Sign every commit21% signed today +3.9 → 63.3 C · #71 of 359

Already done? Suggest a correction Add the trust badge

How Qwen MM Plugins compares in Agent Skills

Bars show each HVTrust score; the tick marks Qwen MM Plugins’s 59.4.

Where the 59.4 comes from

HVTrust dimensions vs the Agent Skills average

59.4 / 100 · 100.0% confidence

Qwen MM Plugins Agent Skills average (359 agents)

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

7.2 / 25

0.8 below avg 8.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

12.7 / 17

0.5 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.4 / 20

5.2 above avg 14.2

AdoptionLog-scaled stars · package downloads

8.4 / 20

0.6 below avg 9.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-26

Rank Moved

Rank dropped 12 spots (#96 → #108)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

Maintainer Checklist

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

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Qwen MM Plugins View Agent Skills Report missing data

80.6

Activity sub-score · out of 100

#109

In Agent Skills

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

Rank Trend

2026-09-29 2026-09-30

Activity & Reach

Stars

3.1k

Forks

201

Last Push

2026-09-23

8 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #109

Analysis

Activity Inputs

80.6 / 100

StarsRepository reach

21.0 / 30

FreshnessLast push recency

23.9 / 25

ActivityRecent commits

24.9 / 25

CommunityFork signal

10.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.9 / 10

OpenSSF Scorecard · scanned Sep 30, 2026

Signed Commits

21%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 8

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 6

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Common questions about Qwen MM Plugins

Qwen MM Plugins has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Qwen MM Plugins publish package provenance?

No published build provenance is currently detected for Qwen MM Plugins. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Qwen MM Plugins have an OpenSSF Scorecard?

Qwen MM Plugins has an OpenSSF Scorecard score of 4.9/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 MM Plugins actively maintained?

Maintained. Last push was 8 days ago.

What license does Qwen MM Plugins use?

Qwen MM Plugins ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Qwen MM Plugins's commits signed?

21% of the last 100 commits to Qwen MM Plugins 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.

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

medium confidence

Implemented

Qwen MM Plugins appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

browser

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 MM Plugins'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

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Qwen MM Plugins?

For maintainers

HVTrust scores Qwen MM Plugins 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-26

Rank Moved

Rank dropped 12 spots (#96 → #108)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 53 spots (#35 → #88)

2026-09-23

HVTrust Changed

HVTrust up 10.5pts (50.2 → 60.7)

2026-09-22

Newly Listed

First tracked at rank #35

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Rank Moved

Rank dropped 14 spots (#54 → #68)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.1/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 121 spots (#163 → #42)

2026-08-29

HVTrust Changed

HVTrust up 35.1pts (25.4 → 60.5)

2026-08-28

Rank Moved

Rank dropped 25 spots (#138 → #163)

2026-08-27

Rank Moved

Rank dropped 20 spots (#118 → #138)

2026-08-26

Rank Moved

Rank dropped 70 spots (#48 → #118)

2026-08-16

Newly Listed

First tracked at rank #55

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/qwen-mm-plugins.svg)](https://hvtracker.net/agents/qwen-mm-plugins)
            
HTML:
            <a href="https://hvtracker.net/agents/qwen-mm-plugins"><img src="https://hvtracker.net/badge/qwen-mm-plugins.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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