updated 2026-11-05 12:09 UTC

Open Multi-Agent

Repository Website

Self-hosted TypeScript agent runtime with durable approvals and verifiable run records. Own it, approve it, audit it.

Multi-Agent Systems TypeScript Listed MIT

Is Open Multi-Agent safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.6 / 10
Provenance None
Signed commits 100%
Last push yesterday
Compare Open Multi-Agent

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Open Multi-Agent scores 61.1/100 (Grade C), ranked #668 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 5.6/10; 100% of recent commits are signed; last pushed 2026-11-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Open Multi-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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Open Multi-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.

  1. Source Signed

    github.com/open-multi-agent/open-multi-agent, MIT, last pushed 2026-11-04. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection4
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies5
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 5
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages None

    No registry package. Open Multi-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

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Open Multi-Agent.

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 Open Multi-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 Open Multi-Agent compares in Multi-Agent Systems

  1. #18 Agency Agents 62.7 +1.6
  2. #19 OpenMontage 61.8 +0.7
  3. #20 Open Multi-Agent 61.1 this agent
  4. #21 Rowboat 60.6 −0.5
  5. #22 TinyTroupe 59.5 −1.6

Bars show each HVTrust score; the tick marks Open Multi-Agent’s 61.1.

Where the 61.1 comes from

HVTrust dimensions vs the Multi-Agent Systems average

61.1 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.0 / 25
3.1 above avg 8.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.1 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
17.8 / 20
4.7 above avg 13.1
AdoptionLog-scaled stars · package downloads
9.2 / 20
1.1 below avg 10.3

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-04
Rank Moved
Rank rose 32 spots (#697 → #665)
2026-10-29
Rank Moved
Rank rose 29 spots (#700 → #671)
2026-10-24
Rank Moved
Rank rose 10 spots (#689 → #679)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.6/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 another agent
View Multi-Agent Systems Report missing data
82.3
Activity sub-score · out of 100
#20
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 →

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
7.0k
Forks
2.4k
Last Push
2026-11-04
yesterday
Commits (4 wk)
29
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
6
Rank Change
▼3
was #665

Analysis

Activity Inputs

82.3 / 100
StarsRepository reach
23.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
18.4 / 25
CommunityFork signal
15.8 / 20

Common questions about Open Multi-Agent

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.6/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?
100% 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.

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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
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-09-13
Mcp Status Changed
Detected MCP server support changed: implemented → declared

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
Rank 29MCP 1
2026-11-04
Rank Moved
Rank rose 32 spots (#697 → #665)
2026-10-29
Rank Moved
Rank rose 29 spots (#700 → #671)
2026-10-24
Rank Moved
Rank rose 10 spots (#689 → #679)
2026-10-14
Rank Moved
Rank dropped 10 spots (#683 → #693)
2026-10-12
Rank Moved
Rank dropped 15 spots (#667 → #682)
2026-10-06
Rank Moved
Rank dropped 10 spots (#636 → #646)
2026-10-05
Rank Moved
Rank dropped 17 spots (#619 → #636)
2026-10-03
Rank Moved
Rank dropped 16 spots (#601 → #617)
2026-09-23
Rank Moved
Rank dropped 349 spots (#228 → #577)
2026-09-21
Rank Moved
Rank rose 347 spots (#575 → #228)
2026-09-20
Rank Moved
Rank dropped 12 spots (#563 → #575)
2026-09-15
Rank Moved
Rank dropped 12 spots (#541 → #553)
2026-09-13
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-09-13
Rank Moved
Rank dropped 62 spots (#478 → #540)
2026-09-09
Rank Moved
Rank dropped 11 spots (#448 → #459)
2026-09-07
Rank Moved
Rank dropped 28 spots (#417 → #445)
2026-09-06
Rank Moved
Rank dropped 10 spots (#407 → #417)
2026-09-05
Rank Moved
Rank dropped 62 spots (#345 → #407)
2026-09-03
Rank Moved
Rank dropped 23 spots (#322 → #345)
2026-09-01
Rank Moved
Rank dropped 14 spots (#308 → #322)
2026-08-31
Rank Moved
Rank dropped 28 spots (#280 → #308)
2026-08-26
Rank Moved
Rank dropped 19 spots (#251 → #270)
2026-08-24
Rank Moved
Rank dropped 14 spots (#229 → #243)
2026-08-22
Rank Moved
Rank rose 14 spots (#243 → #229)
2026-08-19
Rank Moved
Rank dropped 12 spots (#227 → #239)
2026-08-17
Rank Moved
Rank rose 12 spots (#240 → #228)
2026-08-13
Rank Moved
Rank dropped 16 spots (#221 → #237)
2026-08-12
Rank Moved
Rank rose 12 spots (#233 → #221)
2026-08-10
Rank Moved
Rank dropped 16 spots (#222 → #238)
2026-08-08
Rank Moved
Rank dropped 43 spots (#178 → #221)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 61.1 Grade C
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.4 · Raw JSON