updated 2026-10-09 08:15 UTC

Swarm by OpenAI

Repository by openai

Educational framework exploring ergonomic, lightweight multi-agent orchestration. Managed by OpenAI Solution team.

Multi-Agent Systems Python Listed MIT

Is Swarm by OpenAI safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.5 / 10
Provenance None
Signed commits 72%
Last push 177d ago
Compare Swarm by OpenAI

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

Pick any agent to compare →
Suggest a correction

In detail: Swarm by OpenAI scores 44.3/100 (Grade D), ranked #1103 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 3.5/10; 72% of recent commits are signed; last pushed 2026-04-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Swarm by OpenAI 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 Swarm by OpenAI 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/openai/swarm, MIT, last pushed 2026-04-15. 72% 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 3.5/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:

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

  3. Published packages Not linked

    • PyPI openai-swarm Source link isn't a GitHub repo No build attestation

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

Changes to this chain

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

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 Swarm by OpenAI’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 Swarm by OpenAI compares in Multi-Agent Systems

  1. #28 mateclaw 50.8 +6.5
  2. #29 ChatDev 49.8 +5.5
  3. #30 Swarm by OpenAI 44.3 this agent
  4. #31 MiroFlow 41.5 −2.8
  5. #32 swarmclaw 37.9 −6.4

Bars show each HVTrust score; the tick marks Swarm by OpenAI’s 44.3.

Where the 44.3 comes from

HVTrust dimensions vs the Multi-Agent Systems average

44.3 / 100 · 100.0% confidence

Swarm by OpenAI Multi-Agent Systems average (43 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.0 / 25
in line with 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
11.5 / 17
in line with avg 11.8
Maintenance60% last-push freshness · 40% commit activity
0.2 / 20
12.3 below avg 12.5
AdoptionLog-scaled stars · package downloads
14.1 / 20
4.3 above 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 624 spots (#429 → #1053)
2026-09-22
Rank Moved
Rank dropped 73 spots (#356 → #429)
2026-09-21
Rank Moved
Rank rose 692 spots (#1048 → #356)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/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 177 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Swarm by OpenAI View Multi-Agent Systems Report missing data
42.4
Activity sub-score · out of 100
#30
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 177 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
22.0k
Forks
2.3k
Last Push
2026-04-15
177 days ago
Commits (4 wk)
0
Downloads (7d)
594
pypi
HN mentions (30d)
15
Open Issues
28
Rank Change
▼2
was #1101

Analysis

Activity Inputs

42.4 / 100
StarsRepository reach
26.1 / 30
FreshnessLast push recency
0.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
15.7 / 20

Common questions about Swarm by OpenAI

Public trust evidence for Swarm by OpenAI 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 Swarm by OpenAI publish package provenance?
No published build provenance is currently detected for Swarm by OpenAI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Swarm by OpenAI have an OpenSSF Scorecard?
Swarm by OpenAI has an OpenSSF Scorecard score of 3.5/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 Swarm by OpenAI actively maintained?
Slowing down. Last push was 177 days ago — keep an eye on whether activity resumes.
What license does Swarm by OpenAI use?
Swarm by OpenAI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Swarm by OpenAI's commits signed?
72% of the last 100 commits to Swarm by OpenAI 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
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Swarm by OpenAI'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-07-14
Activity Went Stale
No commits for 90 days

Maintain Swarm by OpenAI?

For maintainers

HVTrust scores Swarm by OpenAI 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 30Stale 1HVTrust 1
2026-09-23
Rank Moved
Rank dropped 624 spots (#429 → #1053)
2026-09-22
Rank Moved
Rank dropped 73 spots (#356 → #429)
2026-09-21
Rank Moved
Rank rose 692 spots (#1048 → #356)
2026-09-12
Rank Moved
Rank dropped 10 spots (#1018 → #1028)
2026-09-11
Rank Moved
Rank dropped 11 spots (#1007 → #1018)
2026-09-09
Rank Moved
Rank dropped 17 spots (#988 → #1005)
2026-09-07
Rank Moved
Rank dropped 34 spots (#946 → #980)
2026-09-06
Rank Moved
Rank dropped 14 spots (#932 → #946)
2026-09-05
Rank Moved
Rank dropped 52 spots (#880 → #932)
2026-09-04
Rank Moved
Rank dropped 19 spots (#861 → #880)
2026-09-03
Rank Moved
Rank rose 46 spots (#907 → #861)
2026-09-03
HVTrust Changed
HVTrust up 3.5pts (42.8 → 46.3)
2026-09-02
Rank Moved
Rank dropped 49 spots (#858 → #907)
2026-09-01
Rank Moved
Rank dropped 30 spots (#828 → #858)
2026-08-31
Rank Moved
Rank dropped 35 spots (#793 → #828)
2026-08-30
Rank Moved
Rank dropped 26 spots (#767 → #793)
2026-08-29
Rank Moved
Rank dropped 49 spots (#718 → #767)
2026-08-28
Rank Moved
Rank dropped 29 spots (#689 → #718)
2026-08-27
Rank Moved
Rank dropped 18 spots (#671 → #689)
2026-08-26
Rank Moved
Rank dropped 98 spots (#573 → #671)
2026-08-24
Rank Moved
Rank dropped 13 spots (#558 → #571)
2026-08-19
Rank Moved
Rank dropped 11 spots (#554 → #565)
2026-08-16
Rank Moved
Rank dropped 10 spots (#550 → #560)
2026-08-13
Rank Moved
Rank dropped 14 spots (#535 → #549)
2026-08-12
Rank Moved
Rank rose 11 spots (#546 → #535)
2026-08-10
Rank Moved
Rank dropped 20 spots (#522 → #542)
2026-08-08
Rank Moved
Rank dropped 152 spots (#370 → #522)
2026-07-29
Rank Moved
Rank dropped 11 spots (#346 → #357)
2026-07-15
Rank Moved
Rank dropped 24 spots (#310 → #334)
2026-07-14
Activity Went Stale
No commits for 90 days
2026-07-14
Rank Moved
Rank dropped 17 spots (#293 → #310)
2026-07-13
Rank Moved
Rank dropped 36 spots (#257 → #293)
GitHub → PyPI: openai-swarm

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 44.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/swarm-by-openai.svg)](https://hvtracker.net/agents/swarm-by-openai)
HTML:
<a href="https://hvtracker.net/agents/swarm-by-openai"><img src="https://hvtracker.net/badge/swarm-by-openai.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