How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed today
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
24.9k
Forks
2.5k
Last Push
2026-06-04
today
Commits (4 wk)
383
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
804
Rank Change
▼7
was #74
Analysis
HVTrust Dimensions
68.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
13.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.9 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
10.6 / 20
Activity Inputs
92.2 / 100
StarsRepository reach
26.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.8 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.4 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts3
Branch-Protection0
CI-Tests9
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies6
SAST10
Security-Policy10
Signed-Releases0
Token-Permissions0
Vulnerabilities9
Is Qwen Code safe?
Qwen Code 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 Code publish package provenance?
No published build provenance is currently detected for Qwen Code. 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 Code have an OpenSSF Scorecard?
Qwen Code has an OpenSSF Scorecard score of 6.4/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 Code actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Qwen Code use?
Qwen Code ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Qwen Code's commits signed?
100% of the last 100 commits to Qwen Code 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 Code?
HVTrust scores Qwen Code 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.
Action counts reflect activity on public repos where this agent left detectable fingerprints.
Private repo usage is invisible. Counts are approximate (GitHub Search API caps at 1,000 results per query).
Methodology described in the Provenance Profile spec.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · OSSF Scorecard via deps.dev · GitHub Search API (fingerprint actions)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
