Nexu
The simplest desktop client for OpenClaw 🦞 — bridge your Agent to WeChat, Feishu, Slack & Discord in one click. Works with Claude Code, Codex & any LLM. BYOK, Oauth, local-first, chat from your phone 24/7.
Is Nexu safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Nexu
How does it stack up against its Agent Skills neighbours?
- Claude For Financial Services Cn +0.3 higher
- Super Agent Party +0.1 higher
- Verilog Generator 0.1 lower
In detail: Nexu scores 42.8/100 (Grade D), ranked #301 of 351 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.1/10; 100% of recent commits are signed; last pushed 2026-04-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Nexu compares in Agent Skills
- #299 Claude For Financial Services Cn 43.1 +0.3
- #300 Super Agent Party 42.9 +0.1
- #301 Nexu 42.8 this agent
- #302 Verilog Generator 42.7 −0.1
- #303 Ai Doc Gen 42.7 −0.1
Bars show each HVTrust score; the tick marks Nexu’s 42.8.
Where the 42.8 comes from
HVTrust dimensions vs the Agent Skills average
42.8 / 100 · 100.0% confidenceNexu Agent Skills average (351 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
36.3 / 100Supply Chain Trust
Common questions about Nexu
Does Nexu publish package provenance?
Does Nexu have an OpenSSF Scorecard?
Is Nexu actively maintained?
What license does Nexu use?
Are Nexu's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Nexu'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.
Maintain Nexu?
For maintainers
HVTrust scores Nexu 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/nexu)
<a href="https://hvtracker.net/agents/nexu"><img src="https://hvtracker.net/badge/nexu.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON