GraphCanon rates FedML "Slowing" (36% maintenance signal from public GitHub metadata, computed 2w). Last push was 280 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

Is FedML safe to use?

Last scanned 1mo (deps profile). Status: 88 low - 88 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 FedML as safe - review maintenance, provenance, and scan findings on this page before adopting.

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

Does FedML have known security vulnerabilities?

Last scanned 1mo (deps profile). Status: 88 low - 88 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 FedML trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).

What does GraphCanon never claim about FedML?

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

How does GraphCanon assess trust for FedML?

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/FedML/Trust report

Trust and health report

FedML - trust report

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

GraphCanon updated 2w · GitHub synced 2w

Maintenance

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

Slowing36% signal

last push 280d ago · last release 2y

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 281519510
Not a fork
Verified publisher: organization account
Computed 2w

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: 1mo
Scanner: osv@v1
Stored findings: 88

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-fpfv-jqm9-f5jm

numpy@1.21 · osv@v1

requirements.txt

GHSA-3749-ghw9-m3mg

torch@1.13.1 · osv@v1

requirements.txt

GHSA-53q9-r3pm-6pq6

torch@1.13.1 · osv@v1

requirements.txt

GHSA-5pcm-hx3q-hm94

torch@1.13.1 · osv@v1

requirements.txt

GHSA-887c-mr87-cxwp

torch@1.13.1 · osv@v1

requirements.txt

GHSA-c678-jfcj-6jmf

torch@1.13.1 · osv@v1

requirements.txt

GHSA-f4hp-rmr7-r7v8

torch@1.13.1 · osv@v1

requirements.txt

GHSA-pg7h-5qx3-wjr3

torch@1.13.1 · osv@v1

requirements.txt

GHSA-qfhq-4f3w-5fph

torch@1.13.1 · osv@v1

requirements.txt

GHSA-rrmf-rvhw-rf47

torch@1.13.1 · osv@v1

requirements.txt

GHSA-vgrw-7cvw-pwgx

torch@1.13.1 · osv@v1

requirements.txt

GHSA-x3gm-94wq-g975

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2024-250

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2024-251

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2024-252

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2024-259

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-191

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-198

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-203

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-204

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-205

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-206

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-207

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-208

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-209

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2025-41

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2026-139

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2026-1970

torch@1.13.1 · osv@v1

requirements.txt

PYSEC-2024-38

fastapi@0.92.0 · osv@v1

requirements.txt

GHSA-2fqr-mr3j-6wp8

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-2vrm-gr82-f7m5

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-3wq7-rqq7-wx6j

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-45c4-8wx5-qw6w

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-4fvr-rgm6-gqmc

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-4m7w-qmgq-4wj5

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-54jq-c3m8-4m76

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-5h86-8mv2-jq9f

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-5m98-qgg9-wh84

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-63hf-3vf5-4wqf

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-63hw-fmq6-xxg2

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-69f9-5gxw-wvc2

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-6jhg-hg63-jvvf

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-6mq8-rvhq-8wgg

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-7gpw-8wmc-pm8g

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-8495-4g3g-x7pr

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-8qpw-xqxj-h4r2

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-9548-qrrj-x5pj

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-966j-vmvw-g2g9

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-9x8q-7h8h-wcw9

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-c427-h43c-vf67

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-fh55-r93g-j68g

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-g3cq-j2xw-wf74

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-g84x-mcqj-x9qq

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-gfw2-4jvh-wgfg

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-hcc4-c3v8-rx92

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-hg6j-4rv6-33pg

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-hpj7-wq8m-9hgp

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-jg22-mg44-37j8

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-jj3x-wxrx-4x23

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-m5qp-6w8w-w647

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-m6qw-4cw2-hm4m

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-mqqc-3gqh-h2x8

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-mwh4-6h8g-pg8w

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-p998-jp59-783m

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-pjjw-qhg8-p2p9

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-q3qx-c6g2-7pw2

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-qvrw-v9rv-5rjx

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-w2fm-2cpv-w7v5

aiohttp@3.8.1 · osv@v1

requirements.txt

GHSA-xcgm-r5h9-7989

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2023-120

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2023-246

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2023-250

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2023-251

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2024-24

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2024-26

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1097

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1098

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1099

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1100

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1101

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1102

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1103

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1104

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1105

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1106

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1107

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-1109

aiohttp@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-237

aiohttp@3.8.1 · 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/fedml-ai-fedml/trust.

Common questions

Is FedML maintained?: GraphCanon rates FedML "Slowing" (36% maintenance signal from public GitHub metadata, computed 2w). Last push was 280 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is FedML safe to use?: Last scanned 1mo (deps profile). Status: 88 low - 88 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 FedML as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is FedML a fork?: No. FedML is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does FedML have known security vulnerabilities?: Last scanned 1mo (deps profile). Status: 88 low - 88 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 FedML trust report updated?: Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).
What does GraphCanon never claim about FedML?: We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for FedML. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for FedML?: 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.