Is Open Multi-Agent safe to use?

Open Multi-Agent has an HVTrust score of 64.5/100 (Grade C), ranked #221 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Open Multi-Agent?

Open Multi-Agent scores 64.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.7k GitHub stars and is categorized under Multi-Agent Systems.

Open Multi-Agent

open-multi-agent/open-multi-agent

TypeScript AI agent orchestration framework with dynamic workflows. Describe the goal, not the graph: a coordinator plan

Multi-Agent Systems TypeScript Grade C Listed MIT

64.5/100

Rank #221 of 1204

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.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Rank +3

Is Open Multi-Agent safe? Open Multi-Agent scores 64.5/100 (Grade C), ranked #221 of 1204 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-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#5 Multica — 64.9 (C) → #6 Ruflo — 64.5 (C) → #8 Agency Agents — 63.0 (C) → #9 Concordia — 62.5 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-08

Rank Moved

Rank dropped 43 spots (#178 → #221)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Amazon Bedrock

Maintainer Checklist

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

Compare with AIPass Get email alerts for Open Multi-Agent View Multi-Agent Systems Report missing data

88.7

Activity sub-score · out of 100

In Multi-Agent Systems

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 →

Activity & Reach

Stars

6.7k

Forks

2.4k

Last Push

2026-08-09

today

Commits (4 wk)

126

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #221

Analysis

HVTrust Dimensions vs Multi-Agent Systems

64.5 / 100 · 100.0% confidence

Open Multi-Agent Multi-Agent Systems average (32 agents)

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

11.5 / 25

4.7 above avg 6.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

1.8 above avg 11.2

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.1 above avg 12.9

AdoptionLog-scaled stars · package downloads

9.2 / 20

0.9 below avg 10.1

Activity Inputs

88.7 / 100

StarsRepository reach

23.0 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

97%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 4

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is Open Multi-Agent safe?

Open Multi-Agent 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 Open Multi-Agent publish package provenance?

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

Open Multi-Agent has an OpenSSF Scorecard score of 5.3/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 Open Multi-Agent actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Open Multi-Agent use?

Open Multi-Agent ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Open Multi-Agent's commits signed?

97% of the last 100 commits to Open Multi-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.

Compare Open Multi-Agent head-to-head

Open Multi-Agent vs AIPass → Open Multi-Agent vs Solace Agent Mesh → Open Multi-Agent vs CAMEL →

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

high confidence

Implemented

Open Multi-Agent appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

3 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 Open Multi-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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Amazon Bedrock

2026-08-07

Mcp Status Changed

Detected MCP server support changed: declared → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-08

Rank Moved

Rank dropped 43 spots (#178 → #221)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Amazon Bedrock

2026-08-07

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-07-14

Rank Moved

Rank dropped 13 spots (#182 → #195)

2026-07-13

Rank Moved

Rank dropped 24 spots (#158 → #182)

2026-06-30

Rank Moved

Rank rose 13 spots (#162 → #149)

2026-06-24

Rank Moved

Rank dropped 11 spots (#144 → #155)

2026-06-23

Scorecard Added

OSSF Scorecard: 4.6/10

2026-06-23

Grade Changed

Trust grade D → C

2026-06-23

Rank Moved

Rank rose 116 spots (#260 → #144)

2026-06-23

HVTrust Changed

HVTrust up 36.1pts (26.2 → 62.3)

2026-06-21

Rank Moved

Rank dropped 17 spots (#235 → #252)

2026-06-20

Newly Listed

First tracked at rank #235

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/open-multi-agent.svg)](https://hvtracker.net/agents/open-multi-agent)
            
HTML:
            <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

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.2 · Raw JSON