Is Swarm by OpenAI safe to use?

Swarm by OpenAI has an HVTrust score of 44.4/100 (Grade D), ranked #523 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Swarm by OpenAI?

Swarm by OpenAI scores 44.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 21.9k GitHub stars and is categorized under Multi-Agent Systems.

Swarm by OpenAI

openai/swarm

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

Multi-Agent Systems Python Grade D Listed MIT

44.4/100

Rank #523 of 1204

Compare Swarm by OpenAI

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-04-15 · 116d ago

Recent change

Rank +1

Is Swarm by OpenAI safe? Swarm by OpenAI scores 44.4/100 (Grade D), ranked #523 of 1204 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; recent commits are unsigned; last pushed 2026-04-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#16 Hive — 50.4 (C) → #17 MiroFlow — 45.5 (D) → #19 ChatArena — 39.2 (D) → #20 DeepResearchAgent — 36.0 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 152 spots (#370 → #522)

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

2026-07-29

Rank Moved

Rank dropped 11 spots (#346 → #357)

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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 116 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

50.6

Activity sub-score · out of 100

#18

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 →

Activity & Reach

Stars

21.9k

Forks

2.3k

Last Push

2026-04-15

116 days ago

Commits (4 wk)

Downloads (7d)

297

pypi

HN mentions (30d)

Open Issues

Rank Change

▼1

was #522

Analysis

HVTrust Dimensions vs Multi-Agent Systems

44.4 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

4.4 / 25

2.4 below avg 6.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

11.5 / 17

in line with avg 11.2

Maintenance60% last-push freshness · 40% commit activity

4.3 / 20

8.6 below avg 12.9

AdoptionLog-scaled stars · package downloads

13.7 / 20

3.6 above avg 10.1

Activity Inputs

50.6 / 100

StarsRepository reach

26.0 / 30

FreshnessLast push recency

8.9 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

15.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.5 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

—

Unable to query

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

Is Swarm by OpenAI safe?

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 116 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.

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.

Qdrant

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-08-07

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

2026-07-14

Activity Went Stale

No commits for 90 days

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: OpenAI, Qdrant

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

2026-08-08

Rank Moved

Rank dropped 152 spots (#370 → #522)

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: OpenAI

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)

2026-06-24

Rank Moved

Rank dropped 34 spots (#212 → #246)

2026-06-23

Rank Moved

Rank dropped 16 spots (#196 → #212)

2026-06-21

Rank Moved

Rank dropped 10 spots (#177 → #187)

2026-06-20

Grade Changed

Trust grade C → D

2026-06-20

Rank Moved

Rank dropped 11 spots (#166 → #177)

2026-06-20

HVTrust Changed

HVTrust down 3.7pts (51.7 → 48.0)

2026-06-18

Rank Moved

Rank dropped 13 spots (#147 → #160)

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: OpenAI, Qdrant

2026-06-01

Rank Moved

Rank dropped 17 spots (#107 → #124)

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (41.1 → 51.1)

2026-05-27

Scorecard Added

OSSF Scorecard: 3.5/10

2026-05-27

Grade Changed

Trust grade D → B

2026-05-27

HVTrust Changed

HVTrust up 16.8pts (26.7 → 43.5)

2026-05-25

Newly Listed

First tracked at rank #107

GitHub → PyPI: openai-swarm

Embed Badge Badge guide for maintainers →

For maintainers

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.2 · Raw JSON