Is MetaGPT maintained?

GraphCanon rates MetaGPT "Slowing" (36% maintenance signal from public GitHub metadata, computed Sep 18, 2026). Last push was 239 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

Is MetaGPT safe to use?

Last scanned Sep 18, 2026 (deps profile). Status: 154 low - 154 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify MetaGPT as safe - review maintenance, provenance, and scan findings on this page before adopting.

No. MetaGPT is not flagged as a fork in GitHub metadata at the time of the last refresh.

Does MetaGPT have known security vulnerabilities?

Last scanned Sep 18, 2026 (deps profile). Status: 154 low - 154 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.

How often is the MetaGPT trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 18, 2026 (methodology github_public_v1).

What does GraphCanon never claim about MetaGPT?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for MetaGPT. Signals are sourced heuristics with explicit limits - see trust methodology (https://www.graphcanon.com/trust-methodology).

How does GraphCanon assess trust for MetaGPT?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology (https://www.graphcanon.com/trust-methodology) for full scope and limits.

Home/MetaGPT/Trust report

Trust and health report

MetaGPT - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated Sep 20, 2026 · GitHub synced Sep 20, 2026

68views this month

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Slowing36% signal

last push 239d ago · last release Mar 9, 2025

+637 stars (30d) · +2 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 660551251
Not a fork
Verified publisher: organization account
Computed Sep 18, 2026

Security intelligence

Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.

OSV dependency advisories

Published findings

Last query: Sep 18, 2026
Scanner: osv@v1
Stored findings: 154

View source evidence

deps.dev advisories

Not queried

Scanner: deps.dev@v1

View source evidence

OpenSSF Scorecard

Not queried

Scanner: openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-2fqr-mr3j-6wp8

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-2vrm-gr82-f7m5

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-3wq7-rqq7-wx6j

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-4fvr-rgm6-gqmc

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-4m7w-qmgq-4wj5

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-54jq-c3m8-4m76

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-5h86-8mv2-jq9f

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-5m98-qgg9-wh84

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-63hf-3vf5-4wqf

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-63hw-fmq6-xxg2

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-69f9-5gxw-wvc2

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-6jhg-hg63-jvvf

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-6mq8-rvhq-8wgg

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-7gpw-8wmc-pm8g

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-8495-4g3g-x7pr

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-8qpw-xqxj-h4r2

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-9548-qrrj-x5pj

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-966j-vmvw-g2g9

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-9x8q-7h8h-wcw9

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-c427-h43c-vf67

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-cq5v-8q36-5273

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-fh55-r93g-j68g

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-g3cq-j2xw-wf74

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-g84x-mcqj-x9qq

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-hcc4-c3v8-rx92

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-hg6j-4rv6-33pg

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-hpj7-wq8m-9hgp

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-jg22-mg44-37j8

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-jj3x-wxrx-4x23

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-m5qp-6w8w-w647

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-m6qw-4cw2-hm4m

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-mfx4-hv73-q22v

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-mq44-7p77-q5h7

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-mqqc-3gqh-h2x8

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-mwh4-6h8g-pg8w

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-p998-jp59-783m

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-q3qx-c6g2-7pw2

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-qvrw-v9rv-5rjx

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-w2fm-2cpv-w7v5

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-xcgm-r5h9-7989

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2023-250

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2023-251

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2024-24

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2024-26

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1097

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1098

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1099

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1100

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1101

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1102

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1103

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1104

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1105

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1106

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1107

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-1109

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2094

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2095

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2096

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2097

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2098

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2099

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2100

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2101

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2102

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2103

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2104

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2105

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2106

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2107

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2108

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2109

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2110

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2111

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2112

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-2113

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-237

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-3545

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-3546

aiohttp@3.8.6 · osv@v1

requirements.txt

PYSEC-2026-3547

aiohttp@3.8.6 · osv@v1

requirements.txt

GHSA-5rjg-fvgr-3xxf

setuptools@65.6.3 · osv@v1

requirements.txt

GHSA-cx63-2mw6-8hw5

setuptools@65.6.3 · osv@v1

requirements.txt

GHSA-h35f-9h28-mq5c

setuptools@65.6.3 · osv@v1

requirements.txt

PYSEC-2025-49

setuptools@65.6.3 · osv@v1

requirements.txt

PYSEC-2026-1918

setuptools@65.6.3 · osv@v1

requirements.txt

PYSEC-2026-3447

setuptools@65.6.3 · osv@v1

requirements.txt

GHSA-g7vv-2v7x-gj9p

tqdm@4.66.2 · osv@v1

requirements.txt

PYSEC-2026-1976

tqdm@4.66.2 · osv@v1

requirements.txt

GHSA-7m75-x27w-r52r

qdrant-client@1.7.0 · osv@v1

requirements.txt

PYSEC-2026-509

qdrant-client@1.7.0 · osv@v1

requirements.txt

GHSA-2ww3-72rp-wpp4

semantic-kernel@0.4.3.dev0 · osv@v1

requirements.txt

GHSA-xjw9-4gw8-4rqx

semantic-kernel@0.4.3.dev0 · osv@v1

requirements.txt

PYSEC-2026-163

semantic-kernel@0.4.3.dev0 · osv@v1

requirements.txt

PYSEC-2026-531

semantic-kernel@0.4.3.dev0 · osv@v1

requirements.txt

GHSA-284h-m62q-gf8w

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-2f96-g7mh-g2hx

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-2mqj-m65w-jghx

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-3f7w-8rr8-f37f

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-3rp5-jjmw-4wv2

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-3wxw-xv34-2frg

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-4gmw-gg2m-w46p

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-539m-9xh6-q6rr

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-5xxx-qhh7-9287

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-6p8h-3wgx-97gf

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-7545-fcxq-7j24

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-7833-fr7j-v32q

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-8mcc-hrx5-hvxc

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-94p4-4cq8-9g67

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-956x-8gvw-wg5v

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-9rj7-rf2p-w77r

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-fjr4-x663-mwxc

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-hh9p-6wh2-4mfc

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-hmq2-w58f-27jc

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-jm78-9fvv-mhgr

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-mv93-w799-cj2w

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-p538-c434-8v24

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-r9mr-m37c-5fr3

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-rpm5-65cw-6hj4

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-rwj8-pgh3-r573

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-v87r-6q3f-2j67

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-wvpp-8hx9-p66j

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-x2qx-6953-8485

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2024-4

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-2160

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-2161

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-2162

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-2163

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3783

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3784

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3785

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3786

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3787

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3788

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3836

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3837

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3838

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3839

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3840

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3841

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3842

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3843

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3948

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3949

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3950

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3951

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3952

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3953

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3980

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3981

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3982

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3983

gitpython@3.1.40 · osv@v1

requirements.txt

PYSEC-2026-3984

gitpython@3.1.40 · osv@v1

requirements.txt

GHSA-jw8x-6495-233v

scikit_learn@1.3.2 · osv@v1

requirements.txt

PYSEC-2024-110

scikit_learn@1.3.2 · osv@v1

requirements.txt

Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/foundationagents-metagpt/trust.

Common questions

Is MetaGPT maintained?: GraphCanon rates MetaGPT "Slowing" (36% maintenance signal from public GitHub metadata, computed Sep 18, 2026). Last push was 239 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is MetaGPT safe to use?: Last scanned Sep 18, 2026 (deps profile). Status: 154 low - 154 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify MetaGPT as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is MetaGPT a fork?: No. MetaGPT is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does MetaGPT have known security vulnerabilities?: Last scanned Sep 18, 2026 (deps profile). Status: 154 low - 154 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
How often is the MetaGPT trust report updated?: Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Sep 18, 2026 (methodology github_public_v1).
What does GraphCanon never claim about MetaGPT?: We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for MetaGPT. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for MetaGPT?: Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.