Is Swarm by OpenAI safe?
Swarm by OpenAI scores 45.2/100 (Grade D), ranked #258 of 328 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 →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
45.2/100 · Grade D
Strongest Signal
Adoption
13.7/20
Weakest Signal
Safety / Integrity
4.4/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 3.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signalsThe repo was last pushed 87 days ago. Fresh activity helps separate stable projects from stale ones.
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 refreshed2026-07-11 04:00 UTC·Repo last pushed 87 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
21.8k
Forks
2.3k
Last Push
2026-04-15
87 days ago
Commits (4 wk)
0
Downloads (7d)
297
pypi
HN mentions (30d)
2
Open Issues
30
Rank Change
=
was #258
Analysis
HVTrust Dimensions
45.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
4.4 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.5 / 17
MaintenanceFreshness and commits
6.2 / 20
AdoptionStars and downloads
13.7 / 20
Activity Inputs
54.8 / 100
StarsRepository reach
26.0 / 30
FreshnessLast push recency
12.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 Jul 9, 2026
Signed Commits
—
Unable to query
Binary-Artifacts10
Branch-Protection0
CI-Tests0
CII-Best-Practices0
Code-Review2
Contributors3
Dangerous-Workflow-1
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies-1
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions-1
Vulnerabilities10
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 87 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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
3 tags
Broad capability areas detected.
code
database
search
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-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, Qdrant
Maintain Swarm by OpenAI?
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.
