Is MetaGPT safe?
MetaGPT scores 33.1/100 (Grade D), ranked #310 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 2.4/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 →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
33.1/100 · Grade D
Strongest Signal
Adoption
16.7/20
Weakest Signal
Maintenance
0.6/20
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 2.4/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 171 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 171 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
69.3k
Forks
8.8k
Last Push
2026-01-21
171 days ago
Commits (4 wk)
0
Downloads (7d)
6,735
pypi
HN mentions (30d)
73
Open Issues
25
Rank Change
=
was #310
Analysis
HVTrust Dimensions
33.1 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
4.7 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
10.5 / 17
MaintenanceFreshness and commits
0.6 / 20
AdoptionStars and downloads
16.7 / 20
Activity Inputs
48.8 / 100
StarsRepository reach
29.0 / 30
FreshnessLast push recency
1.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
18.4 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
2.4 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
33%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests3
CII-Best-Practices0
Code-Review5
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
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.4/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?
Slowing down. Last push was 171 days ago — keep an eye on whether activity resumes.
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.
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:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
4 tags
Broad capability areas detected.
browser
code
database
shell
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-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?
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.
