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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 92 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
16.5k
Forks
1.6k
Last Push
2026-03-04
92 days ago
Commits (4 wk)
0
Downloads (7d)
90,789
pypi
HN mentions (30d)
0
Open Issues
502
Rank Change
▼9
was #137
Analysis
HVTrust Dimensions
50.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.6 / 17
MaintenanceFreshness and commits
5.9 / 20
AdoptionStars and downloads
16.7 / 20
Activity Inputs
52.6 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
12.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.9 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.6 / 10
via deps.dev · OpenSSF
Signed Commits
14%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests0
CII-Best-Practices0
Code-Review1
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies1
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions10
Vulnerabilities0
Is Qwen Agent safe?
Public trust evidence for Qwen Agent is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Qwen Agent publish package provenance?
No published build provenance is currently detected for Qwen Agent. 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 Agent have an OpenSSF Scorecard?
Qwen Agent has an OpenSSF Scorecard score of 3.6/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 Agent actively maintained?
Slowing down. Last push was 92 days ago — keep an eye on whether activity resumes.
What license does Qwen Agent use?
Qwen Agent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Qwen Agent's commits signed?
14% of the last 100 commits to Qwen 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Qwen Agent?
HVTrust scores Qwen 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.
