updated 2026-10-09 08:15 UTC

SwarmZero

Repository Website

SwarmZero's SDK for building AI agents, swarms of agents and much more.

Multi-Agent Systems Python Needs review Apache-2.0

Is SwarmZero safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.6 / 10
Provenance None
Signed commits 63%
Last push 429d ago
Advisories None known
Compare SwarmZero

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

Pick any agent to compare →
Suggest a correction

In detail: SwarmZero scores 26.5/100 (Grade D), ranked #1326 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.6/10; 63% of recent commits are signed; no published advisory affects its latest release (swarmzero); last pushed 2025-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How SwarmZero 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
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-08-06)

Chain of custody

Scanners check what the code says. This traces who ships SwarmZero 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 Partly signed

    github.com/swarmzero/swarmzero, Apache-2.0, last pushed 2025-08-06. 63% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

    • Code Review3
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 3
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI swarmzero 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: swarmzero 0.0.3. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

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

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

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

Verify this score yourself

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

  1. #38 WorldSeed 30.6 +4.1
  2. #39 ChatArena 29.2 +2.7
  3. #40 SwarmZero 26.5 this agent
  4. #41 OpenBot 26.3 −0.2
  5. #42 MassGen 19.9 −6.6

Bars show each HVTrust score; the tick marks SwarmZero’s 26.5.

Where the 26.5 comes from

HVTrust dimensions vs the Multi-Agent Systems average

26.5 / 100 · 100.0% confidence

SwarmZero Multi-Agent Systems average (43 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.4 / 25
1.8 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.1
Transparency50% declared license · 50% OSSF Scorecard
10.7 / 17
1.1 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.5 below avg 12.5
AdoptionLog-scaled stars · package downloads
7.4 / 20
2.4 below avg 9.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 373 spots (#936 → #1309)
2026-09-22
Rank Moved
Rank dropped 507 spots (#429 → #936)
2026-09-21
Rank Moved
Rank rose 877 spots (#1306 → #429)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.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.
Refresh maintenance signals The repo was last pushed 429 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-08-06)
Compare with another agent Get email alerts for SwarmZero View Multi-Agent Systems Report missing data
22.7
Activity sub-score · out of 100
#40
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed 429 days ago — may be stale

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
276
Forks
52
Last Push
2025-08-06
429 days ago
Commits (4 wk)
0
Downloads (7d)
13
pypi
HN mentions (30d)
1
Open Issues
0
Rank Change
=
was #1326

Analysis

Activity Inputs

22.7 / 100
StarsRepository reach
14.7 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.0 / 20

Common questions about SwarmZero

Public trust evidence for SwarmZero is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does SwarmZero publish package provenance?
No published build provenance is currently detected for SwarmZero. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does SwarmZero have an OpenSSF Scorecard?
SwarmZero has an OpenSSF Scorecard score of 2.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 SwarmZero actively maintained?
Stale. The repository has not been pushed to in 429 days. Consider whether the project is still being maintained.
What license does SwarmZero use?
SwarmZero ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SwarmZero's commits signed?
62% of the last 100 commits to SwarmZero 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
None detected
No MCP server signal detected.
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
medium confidence
1 tags
Broad capability areas detected.
  • database
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

Maintain SwarmZero?

For maintainers

HVTrust scores SwarmZero 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 23Warning Issued 1
2026-09-23
Rank Moved
Rank dropped 373 spots (#936 → #1309)
2026-09-22
Rank Moved
Rank dropped 507 spots (#429 → #936)
2026-09-21
Rank Moved
Rank rose 877 spots (#1306 → #429)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1269 → #1284)
2026-09-05
Rank Moved
Rank dropped 13 spots (#1256 → #1269)
2026-09-04
Rank Moved
Rank dropped 17 spots (#1239 → #1256)
2026-09-03
Rank Moved
Rank dropped 35 spots (#1204 → #1239)
2026-09-02
Rank Moved
Rank dropped 35 spots (#1169 → #1204)
2026-09-01
Rank Moved
Rank dropped 43 spots (#1126 → #1169)
2026-08-31
Rank Moved
Rank dropped 30 spots (#1096 → #1126)
2026-08-30
Rank Moved
Rank dropped 48 spots (#1048 → #1096)
2026-08-29
Rank Moved
Rank dropped 50 spots (#998 → #1048)
2026-08-28
Rank Moved
Rank dropped 37 spots (#961 → #998)
2026-08-27
Rank Moved
Rank dropped 26 spots (#935 → #961)
2026-08-26
Rank Moved
Rank dropped 111 spots (#824 → #935)
2026-08-19
Rank Moved
Rank dropped 10 spots (#816 → #826)
2026-08-16
Rank Moved
Rank dropped 17 spots (#808 → #825)
2026-08-10
Rank Moved
Rank dropped 45 spots (#759 → #804)
2026-08-08
Rank Moved
Rank dropped 323 spots (#430 → #753)
2026-08-06
Warning Issued
Warning: eligibility issues detected
2026-07-29
Rank Moved
Rank dropped 11 spots (#391 → #402)
2026-07-15
Rank Moved
Rank dropped 25 spots (#364 → #389)
2026-07-14
Rank Moved
Rank dropped 20 spots (#344 → #364)
2026-07-13
Rank Moved
Rank dropped 36 spots (#308 → #344)
GitHub → Website → PyPI: swarmzero

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 26.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/swarmzero.svg)](https://hvtracker.net/agents/swarmzero)
HTML:
<a href="https://hvtracker.net/agents/swarmzero"><img src="https://hvtracker.net/badge/swarmzero.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 · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON