Open Multi-Agent
From a goal to a task DAG, automatically. TypeScript-native multi-agent orchestration.
Compare Open Multi-Agent
How does it stack up against its Multi-Agent Systems neighbours?
Pick any agent to compare →Promising trust profile, but some evidence still deserves review.
Is Open Multi-Agent safe? Open Multi-Agent scores 60.9/100 (Grade C), ranked #206 of 468 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 5.3/10; 97% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in Multi-Agent Systems
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 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
Activity & Reach
Analysis
HVTrust Dimensions vs Multi-Agent Systems
60.9 / 100 · 100.0% confidenceOpen Multi-Agent Multi-Agent Systems average (28 agents)
Activity Inputs
88.4 / 100Supply Chain Trust
Is Open Multi-Agent safe?
Does Open Multi-Agent publish package provenance?
Does Open Multi-Agent have an OpenSSF Scorecard?
Is Open Multi-Agent actively maintained?
What license does Open Multi-Agent use?
Are Open Multi-Agent'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.
Compare Open Multi-Agent head-to-head
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 →
- code
- filesystem
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Open Multi-Agent?
For maintainers
HVTrust scores Open Multi-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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/open-multi-agent)
<a href="https://hvtracker.net/agents/open-multi-agent"><img src="https://hvtracker.net/badge/open-multi-agent.svg" alt="HVTrust"></a>
Other agents in Multi-Agent Systems
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON