GPTSwarm

🐝 The First Self-Improving agents with RL / Prompting Optimization

Multi-Agent Systems Python Grade D Listed MIT
37.3/100
Rank #1206 of 1328
Compare GPTSwarm

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-02-05 · 225d ago
Recent change
No recent signal change

Is GPTSwarm safe? GPTSwarm scores 37.3/100 (Grade D), ranked #1206 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.8/10; 87% of recent commits are signed; last pushed 2026-02-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-09
Rank Moved
Rank dropped 12 spots (#1181 → #1193)
2026-09-08
Rank Moved
Rank dropped 13 spots (#1168 → #1181)
2026-09-07
Rank Moved
Rank dropped 12 spots (#1156 → #1168)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/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 225 days ago. Fresh activity helps separate stable projects from stale ones.
27.6
Activity sub-score · out of 100
#30

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-18 13:03 UTC · Repo last pushed 225 days ago — may be stale

Rank Trend

2026-08-11 2026-09-18

Activity & Reach

Stars
1.0k
Forks
107
Last Push
2026-02-05
225 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼1
was #1205

Analysis

HVTrust Dimensions vs Multi-Agent Systems

37.3 / 100 · 100.0% confidence

GPTSwarm Multi-Agent Systems average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.1 / 25
0.7 above avg 8.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.2
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.4 below avg 12.4
AdoptionLog-scaled stars · package downloads
7.2 / 20
2.9 below avg 10.1

Activity Inputs

27.6 / 100
StarsRepository reach
18.1 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.8 / 10
OpenSSF Scorecard · scanned Sep 14, 2026
Signed Commits
87%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 0
CII-Best-Practices 0
Code-Review 1
Contributors 10
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 10
Vulnerabilities 0

Is GPTSwarm safe?

Public trust evidence for GPTSwarm 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 GPTSwarm publish package provenance?
No published build provenance is currently detected for GPTSwarm. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does GPTSwarm have an OpenSSF Scorecard?
GPTSwarm has an OpenSSF Scorecard score of 3.8/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 GPTSwarm actively maintained?
Stale. The repository has not been pushed to in 225 days. Consider whether the project is still being maintained.
What license does GPTSwarm use?
GPTSwarm ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are GPTSwarm's commits signed?
87% of the last 100 commits to GPTSwarm 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
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain GPTSwarm?

For maintainers

HVTrust scores GPTSwarm 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.

Reputation Timeline

Signal history
Rank 19Listed 1HVTrust 1Scorecard 1
2026-09-09
Rank Moved
Rank dropped 12 spots (#1181 → #1193)
2026-09-08
Rank Moved
Rank dropped 13 spots (#1168 → #1181)
2026-09-07
Rank Moved
Rank dropped 12 spots (#1156 → #1168)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1141 → #1156)
2026-09-05
Rank Moved
Rank dropped 35 spots (#1106 → #1141)
2026-09-04
Rank Moved
Rank dropped 20 spots (#1086 → #1106)
2026-09-03
Rank Moved
Rank dropped 51 spots (#1035 → #1086)
2026-09-02
Rank Moved
Rank dropped 43 spots (#992 → #1035)
2026-09-01
Rank Moved
Rank dropped 44 spots (#948 → #992)
2026-08-31
Rank Moved
Rank dropped 31 spots (#917 → #948)
2026-08-30
Rank Moved
Rank dropped 44 spots (#873 → #917)
2026-08-29
Rank Moved
Rank dropped 47 spots (#826 → #873)
2026-08-28
Rank Moved
Rank dropped 23 spots (#803 → #826)
2026-08-27
Rank Moved
Rank dropped 22 spots (#781 → #803)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.8/10
2026-08-26
Rank Moved
Rank rose 498 spots (#1279 → #781)
2026-08-26
HVTrust Changed
HVTrust up 23.3pts (14.0 → 37.3)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1260 → #1285)
2026-08-10
Rank Moved
Rank dropped 79 spots (#1179 → #1258)
2026-08-08
Rank Moved
Rank dropped 667 spots (#512 → #1179)
2026-08-06
Rank Moved
Rank dropped 43 spots (#463 → #506)
2026-08-03
Newly Listed
First tracked at rank #463

Embed Badge Badge guide for maintainers →

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

Other agents in Multi-Agent Systems

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