updated 2026-09-20 21:02 UTC

agent-swarm

desplega-ai/agent-swarm

Your Company Agentic Operating System

Multi-Agent Systems TypeScript Grade B Listed MIT
65.6/100
Rank #445 of 1328
Compare agent-swarm

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-09-20 · 0d ago
Recent change
Rank +4

Is agent-swarm safe? agent-swarm scores 65.6/100 (Grade B), ranked #445 of 1328 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 6.7/10; 100% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#6 Ruflo — 66.4 (B) → #7 Multica — 65.8 (B) → #9 Agency Agents — 63.9 (C) → #10 Rakazo — 63.8 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-18
Rank Moved
Rank dropped 10 spots (#435 → #445)
2026-09-16
Grade Changed
Trust grade C → B
2026-09-16
Rank Moved
Rank rose 57 spots (#494 → #437)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.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.
Compare with AIPass Get email alerts for agent-swarm View Multi-Agent Systems Report missing data
76.9
Activity sub-score · out of 100
#8
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 B 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-09-20 21:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
813
Forks
105
Last Push
2026-09-20
today
Commits (4 wk)
256
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
10
Rank Change
▲3
was #448

Analysis

HVTrust Dimensions vs Multi-Agent Systems

65.6 / 100 · 100.0% confidence

agent-swarm Multi-Agent Systems average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.4 / 25
5.1 above avg 8.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
14.2 / 17
2.2 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.6 above avg 12.4
AdoptionLog-scaled stars · package downloads
7.0 / 20
3.1 below avg 10.1

Activity Inputs

76.9 / 100
StarsRepository reach
17.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
9.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.7 / 10
OpenSSF Scorecard · scanned Sep 18, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 8
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 6
SAST 10
Security-Policy 10
Signed-Releases 0
Token-Permissions 6
Vulnerabilities 0

Is agent-swarm safe?

agent-swarm 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 agent-swarm publish package provenance?
No published build provenance is currently detected for agent-swarm. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does agent-swarm have an OpenSSF Scorecard?
agent-swarm has an OpenSSF Scorecard score of 6.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 agent-swarm actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does agent-swarm use?
agent-swarm ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are agent-swarm's commits signed?
100% of the last 100 commits to agent-swarm 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 agent-swarm head-to-head

agent-swarm vs AIPass → agent-swarm vs Swarms → agent-swarm vs Solace Agent Mesh →

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
agent-swarm appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 agent-swarm'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-15
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-09
Provider Removed
Runtime surface shrank — no longer detected: OpenRouter
2026-09-04
Provider Added
Runtime surface grew — new detected provider dependency: OpenRouter

Maintain agent-swarm?

For maintainers

HVTrust scores agent-swarm 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 23Grade 2Surface 2Listed 1HVTrust 1Scorecard 1Surface 1
2026-09-18
Rank Moved
Rank dropped 10 spots (#435 → #445)
2026-09-16
Grade Changed
Trust grade C → B
2026-09-16
Rank Moved
Rank rose 57 spots (#494 → #437)
2026-09-15
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-15
Rank Moved
Rank dropped 14 spots (#480 → #494)
2026-09-12
Rank Moved
Rank rose 12 spots (#488 → #476)
2026-09-11
Rank Moved
Rank dropped 11 spots (#477 → #488)
2026-09-09
Provider Removed
Runtime surface shrank — no longer detected: OpenRouter
2026-09-09
Rank Moved
Rank rose 49 spots (#529 → #480)
2026-09-08
Rank Moved
Rank dropped 10 spots (#519 → #529)
2026-09-07
Rank Moved
Rank dropped 34 spots (#485 → #519)
2026-09-05
Rank Moved
Rank dropped 72 spots (#408 → #480)
2026-09-04
Provider Added
Runtime surface grew — new detected provider dependency: OpenRouter
2026-09-04
Rank Moved
Rank dropped 67 spots (#341 → #408)
2026-09-03
Rank Moved
Rank dropped 16 spots (#325 → #341)
2026-09-01
Scorecard Added
OSSF Scorecard: 6.3/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 805 spots (#1133 → #328)
2026-09-01
HVTrust Changed
HVTrust up 38.8pts (25.1 → 63.9)
2026-08-31
Rank Moved
Rank dropped 31 spots (#1102 → #1133)
2026-08-30
Rank Moved
Rank dropped 46 spots (#1056 → #1102)
2026-08-29
Rank Moved
Rank dropped 50 spots (#1006 → #1056)
2026-08-28
Rank Moved
Rank dropped 36 spots (#970 → #1006)
2026-08-27
Rank Moved
Rank dropped 24 spots (#946 → #970)
2026-08-26
Rank Moved
Rank dropped 106 spots (#840 → #946)
2026-08-24
Rank Moved
Rank dropped 11 spots (#829 → #840)
2026-08-16
Rank Moved
Rank dropped 17 spots (#827 → #844)
2026-08-12
Rank Moved
Rank rose 10 spots (#827 → #817)
2026-08-10
Rank Moved
Rank dropped 45 spots (#781 → #826)
2026-08-08
Rank Moved
Rank dropped 333 spots (#441 → #774)
2026-08-06
Newly Listed
First tracked at rank #480
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.6 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/agent-swarm.svg)](https://hvtracker.net/agents/agent-swarm)
HTML:
<a href="https://hvtracker.net/agents/agent-swarm"><img src="https://hvtracker.net/badge/agent-swarm.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.3 · Raw JSON