Is MetaGPT safe to use?

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

What is the trust score for MetaGPT?

MetaGPT scores 34.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 69.7k GitHub stars and is categorized under Multi-Agent Systems.

MetaGPT

FoundationAgents/MetaGPT

🌟 The Multi-Agent Framework: First AI Software Company, Towards Natural Language Programming

Multi-Agent Systems Python Grade D Listed MIT

34.1/100

Rank #679 of 1204

Compare MetaGPT

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-01-21 · 200d ago

Recent change

Rank +1

Is MetaGPT safe? MetaGPT scores 34.1/100 (Grade D), ranked #679 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 2.3/10; 33% of recent commits are signed; last pushed 2026-01-21. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Multi-Agent Systems

#19 ChatArena — 39.2 (D) → #20 DeepResearchAgent — 36.0 (D) → #22 SwarmZero — 26.4 (D) → #23 agent-swarm — 25.1 (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 264 spots (#414 → #678)

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Azure OpenAI

2026-07-29

Rank Moved

Rank dropped 12 spots (#397 → #409)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.3/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 200 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for MetaGPT View Multi-Agent Systems Report missing data

47.5

Activity sub-score · out of 100

#21

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

69.7k

Forks

8.9k

Last Push

2026-01-21

200 days ago

Commits (4 wk)

Downloads (7d)

6,735

pypi

HN mentions (30d)

Open Issues

Rank Change

▼1

was #678

Analysis

HVTrust Dimensions vs Multi-Agent Systems

34.1 / 100 · 100.0% confidence

MetaGPT Multi-Agent Systems average (32 agents)

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

4.5 / 25

2.3 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

10.5 / 17

0.7 below avg 11.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.9 below avg 12.9

AdoptionLog-scaled stars · package downloads

16.7 / 20

6.6 above avg 10.1

Activity Inputs

47.5 / 100

StarsRepository reach

29.1 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

18.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.3 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

33%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 1

CII-Best-Practices 0

Code-Review 5

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is MetaGPT safe?

Public trust evidence for MetaGPT 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 MetaGPT publish package provenance?

No published build provenance is currently detected for MetaGPT. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MetaGPT have an OpenSSF Scorecard?

MetaGPT has an OpenSSF Scorecard score of 2.3/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 MetaGPT actively maintained?

Stale. The repository has not been pushed to in 200 days. Consider whether the project is still being maintained.

What license does MetaGPT use?

MetaGPT ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MetaGPT's commits signed?

33% of the last 100 commits to MetaGPT 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

6 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

3 tags

Broad capability areas detected.

browser
code
database

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Warning

1 package source mismatch detected

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 MetaGPT'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: Azure OpenAI

2026-06-16

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-15

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-13

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-11

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-10

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

Maintain MetaGPT?

For maintainers

HVTrust scores MetaGPT 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 264 spots (#414 → #678)

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Azure OpenAI

2026-07-29

Rank Moved

Rank dropped 12 spots (#397 → #409)

2026-07-15

Rank Moved

Rank dropped 24 spots (#367 → #391)

2026-07-14

Rank Moved

Rank dropped 21 spots (#346 → #367)

2026-07-13

Rank Moved

Rank dropped 36 spots (#310 → #346)

2026-06-24

Rank Moved

Rank dropped 31 spots (#231 → #262)

2026-06-23

Rank Moved

Rank dropped 18 spots (#213 → #231)

2026-06-22

Rank Moved

Rank dropped 10 spots (#203 → #213)

2026-06-21

Rank Moved

Rank dropped 11 spots (#192 → #203)

2026-06-18

Scorecard Added

OSSF Scorecard: 2.4/10

2026-06-18

Rank Moved

Rank rose 27 spots (#212 → #185)

2026-06-18

HVTrust Changed

HVTrust up 14.9pts (29.9 → 44.8)

2026-06-16

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-16

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-16

Rank Moved

Rank dropped 35 spots (#175 → #210)

2026-06-16

HVTrust Changed

HVTrust down 15.0pts (45.1 → 30.1)

2026-06-15

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-15

Scorecard Added

OSSF Scorecard: 2.4/10

2026-06-15

Rank Moved

Rank rose 33 spots (#208 → #175)

2026-06-15

HVTrust Changed

HVTrust up 14.9pts (30.2 → 45.1)

2026-06-13

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-13

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-13

Rank Moved

Rank dropped 33 spots (#175 → #208)

2026-06-13

HVTrust Changed

HVTrust down 15.1pts (45.3 → 30.2)

2026-06-11

Drift Warning Cleared

Provenance drift warning cleared (now: match)

2026-06-11

Scorecard Added

OSSF Scorecard: 2.4/10

2026-06-11

Rank Moved

Rank rose 32 spots (#207 → #175)

2026-06-11

HVTrust Changed

HVTrust up 15.0pts (30.4 → 45.4)

2026-06-10

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-06-10

Scorecard Removed

OSSF Scorecard no longer detected

2026-06-10

Rank Moved

Rank dropped 43 spots (#164 → #207)

2026-06-10

HVTrust Changed

HVTrust down 15.1pts (45.5 → 30.4)

2026-06-09

Newly Listed

First tracked at rank #164

GitHub → PyPI: metagpt

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/metagpt.svg)](https://hvtracker.net/agents/metagpt)
            
HTML:
            <a href="https://hvtracker.net/agents/metagpt"><img src="https://hvtracker.net/badge/metagpt.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