Is Yunjue-Agent safe to use?

Yunjue-Agent has an HVTrust score of 29.3/100 (Grade D), ranked #1340 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Yunjue-Agent?

Yunjue-Agent scores 29.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 545 GitHub stars and is categorized under Agent Frameworks.

Yunjue-Agent

Repository Website

Yunjue Agent: A Fully Reproducible, Zero-Start In-Situ Self-Evolving Agent System for Open-Ended Tasks

Agent Frameworks Python Listed Apache-2.0

Is Yunjue-Agent safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.7 / 10

Provenance None

Signed commits 26%

Last push 244d ago

Compare Yunjue-Agent

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Yunjue-Agent scores 29.3/100 (Grade D), ranked #1340 of 1374 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 1.7/10; 26% of recent commits are signed; last pushed 2026-03-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How Yunjue-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 1.7 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +15.3 → 44.6 D · #107 of 130
Sign every commit26% signed today +3.6 → 32.9 D · #118 of 130

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Yunjue-Agent and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/YunjueTech/Yunjue-Agent, Apache-2.0, last pushed 2026-03-06. 26% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 1.7/10 (scanned Oct 31, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0
Published packages None

No registry package. Yunjue-Agent is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-09-01 OSSF Scorecard: 1.7/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Yunjue-Agent’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Yunjue-Agent compares in Agent Frameworks

Bars show each HVTrust score; the tick marks Yunjue-Agent’s 29.3.

Where the 29.3 comes from

HVTrust dimensions vs the Agent Frameworks average

29.3 / 100 · 100.0% confidence

Yunjue-Agent Agent Frameworks average (130 agents)

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

3.5 / 25

6.6 below avg 10.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

9.9 / 17

2.6 below avg 12.5

Maintenance60% last-push freshness · 40% commit activity

0 / 20

14.7 below avg 14.7

AdoptionLog-scaled stars · package downloads

6.6 / 20

4.7 below avg 11.3

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-09

Rank Moved

Rank dropped 11 spots (#1312 → #1323)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.7/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.

Refresh maintenance signals The repo was last pushed 244 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View Agent Frameworks Report missing data

24.9

Activity sub-score · out of 100

#125

In Agent Frameworks

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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-11-05

Activity & Reach

Stars

545

Forks

Last Push

2026-03-06

244 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #1340

Analysis

Activity Inputs

24.9 / 100

StarsRepository reach

16.4 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.5 / 20

Common questions about Yunjue-Agent

Public trust evidence for Yunjue-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 Yunjue-Agent publish package provenance?

No published build provenance is currently detected for Yunjue-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 Yunjue-Agent have an OpenSSF Scorecard?

Yunjue-Agent has an OpenSSF Scorecard score of 1.7/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 Yunjue-Agent actively maintained?

Stale. The repository has not been pushed to in 244 days. Consider whether the project is still being maintained.

What license does Yunjue-Agent use?

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

Are Yunjue-Agent's commits signed?

26% of the last 100 commits to Yunjue-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.

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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies 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

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

Provider Added

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

Maintain Yunjue-Agent?

For maintainers

HVTrust scores Yunjue-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-10-09

Rank Moved

Rank dropped 11 spots (#1312 → #1323)

2026-09-23

Provider Added

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

2026-09-23

Rank Moved

Rank dropped 159 spots (#1138 → #1297)

2026-09-23

HVTrust Changed

HVTrust up 8.4pts (20.9 → 29.3)

2026-09-22

Newly Listed

First tracked at rank #1138

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-06

Rank Moved

Rank dropped 14 spots (#1252 → #1266)

2026-09-05

Rank Moved

Rank dropped 20 spots (#1232 → #1252)

2026-09-04

Rank Moved

Rank dropped 16 spots (#1216 → #1232)

2026-09-03

Rank Moved

Rank dropped 41 spots (#1175 → #1216)

2026-09-02

Rank Moved

Rank dropped 40 spots (#1135 → #1175)

2026-09-01

Scorecard Added

OSSF Scorecard: 1.7/10

2026-09-01

Rank Moved

Rank rose 179 spots (#1314 → #1135)

2026-09-01

HVTrust Changed

HVTrust up 17.2pts (12.1 → 29.3)

2026-08-16

Rank Moved

Rank dropped 25 spots (#1272 → #1297)

2026-08-10

Rank Moved

Rank dropped 79 spots (#1193 → #1272)

2026-08-08

Rank Moved

Rank dropped 676 spots (#517 → #1193)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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

Yunjue-Agent

How Yunjue-Agent could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Yunjue-Agent compares in Agent Frameworks

Where the 29.3 comes from

HVTrust dimensions vs the Agent Frameworks average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Yunjue-Agent

AI agent surface

Maintain Yunjue-Agent?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Frameworks