updated 2026-10-21 20:07 UTC

Swarms

Repository Website

The Enterprise-Grade Multi-Agent Orchestration Framework. Website: https://swarms.ai

Multi-Agent Systems Python Listed Apache-2.0

Is Swarms safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.4 / 10
Provenance None
Signed commits 100%
Last push today
Advisories None known
Compare Swarms

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

Pick any agent to compare →
Suggest a correction

In detail: Swarms scores 74.1/100 (Grade B), ranked #268 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.4/10; 100% of recent commits are signed; no published advisory affects its latest release (swarms); last pushed 2026-10-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Swarms 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 Swarms and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/kyegomez/swarms, Apache-2.0, last pushed 2026-10-21. 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 6.4/10 (scanned Oct 19, 2026). The checks that decide who can get a change released:

    • Code Review8
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    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 -1
    Pinned-Dependencies 1
    SAST 7
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI swarms Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: swarms 16.0.1. No published advisory affects it (OSV, checked 2026-10-21).

Changes to this chain

  • 2026-09-12 OSSF Scorecard: 6.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Swarms’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 Swarms compares in Multi-Agent Systems

  1. #1 AIPass 86.4 +12.3
  2. #2 OpenMausBot 83.6 +9.5
  3. #3 Swarms 74.1 this agent
  4. #4 Solace Agent Mesh 68.8 −5.3
  5. #5 Ruflo 68.4 −5.7

Bars show each HVTrust score; the tick marks Swarms’s 74.1.

Where the 74.1 comes from

HVTrust dimensions vs the Multi-Agent Systems average

74.1 / 100 · 100.0% confidence

Swarms Multi-Agent Systems average (43 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.0 / 25
4.2 above avg 8.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
13.9 / 17
1.7 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.9 above avg 13.1
AdoptionLog-scaled stars · package downloads
13.9 / 20
3.7 above avg 10.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-19
Rank Moved
Rank rose 16 spots (#285 → #269)
2026-10-09
Rank Moved
Rank dropped 17 spots (#270 → #287)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → marketplace
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.4/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 Swarms View Multi-Agent Systems Report missing data
87.2
Activity sub-score · out of 100
#3
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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-21 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-21

Activity & Reach

Stars
7.3k
Forks
1.0k
Last Push
2026-10-21
today
Commits (4 wk)
161
Downloads (7d)
3,144
pypi
HN mentions (30d)
—
Open Issues
148
Rank Change
▼1
was #267

Analysis

Activity Inputs

87.2 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.0 / 20

Common questions about Swarms

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

Swarms vs AIPass → Swarms vs OpenMausBot → Swarms 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
Swarms 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: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Marketplace
Marketplace plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Swarms'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-23
Tool Surface Changed
Detected tool/plugin surface changed: none → marketplace
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Groq, Multi-provider (LiteLLM), OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Swarms?

For maintainers

HVTrust scores Swarms 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 5HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-10-19
Rank Moved
Rank rose 16 spots (#285 → #269)
2026-10-09
Rank Moved
Rank dropped 17 spots (#270 → #287)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → marketplace
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Groq, Multi-provider (LiteLLM), OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 314 spots (#577 → #263)
2026-09-23
HVTrust Changed
HVTrust up 37.6pts (35.3 → 72.9)
2026-09-22
Newly Listed
First tracked at rank #577
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Scorecard Added
OSSF Scorecard: 6.1/10
2026-09-12
Grade Changed
Trust grade D → B
2026-09-12
Rank Moved
Rank rose 876 spots (#1125 → #249)
2026-09-12
HVTrust Changed
HVTrust up 32.4pts (41.3 → 73.7)
2026-09-10
Rank Moved
Rank rose 182 spots (#1306 → #1124)
2026-09-10
HVTrust Changed
HVTrust up 17.4pts (23.9 → 41.3)
2026-09-08
Newly Listed
First tracked at rank #1302
GitHub → Website → PyPI: swarms

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 74.1 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/swarms.svg)](https://hvtracker.net/agents/swarms)
HTML:
<a href="https://hvtracker.net/agents/swarms"><img src="https://hvtracker.net/badge/swarms.svg" alt="HVTrust"></a>

Other agents in Multi-Agent Systems

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON