Is Fedml safe to use?

Fedml has an HVTrust score of 45.1/100 (Grade D), ranked #1121 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Fedml?

Fedml scores 45.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.1k GitHub stars and is categorized under Agent Frameworks.

Fedml

Repository

Website

FEDML - The unified and scalable ML library for large-scale distributed training, model serving, and federated learning. FEDML Launch, a cross-cloud scheduler, further enables running any AI jobs on any GPU cloud or on-premise cluster. Built on this library, TensorOpera AI (https://TensorOpera.ai)…

Agent Frameworks Python Listed Apache-2.0

Is Fedml safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4 / 10

Provenance None

Signed commits 37%

Last push 354d ago

Advisories None known

Compare Fedml

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Fedml scores 45.1/100 (Grade D), ranked #1121 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4/10; 37% of recent commits are signed; no published advisory affects its latest release (fedml); last pushed 2025-10-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How Fedml could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.6 → 59.7 C · #66 of 130
Raise the OSSF Scorecard from 4 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Maintained 0 +10.4 → 55.5 C · #80 of 130
Sign every commit37% signed today +3.1 → 48.2 D · #96 of 130

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Fedml and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/FedML-AI/FedML, Apache-2.0, last pushed 2025-10-28. 37% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Oct 17, 2026). The checks that decide who can get a change released:
- Code Review9
- Branch Protectionn/a
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 14 Scorecard checks

Binary-Artifacts 4

Branch-Protection -1

CII-Best-Practices 0

Code-Review 9

Dangerous-Workflow 10

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 7

Security-Policy 0

Signed-Releases -1

Token-Permissions 0
Published packages Linked, not attested
- PyPI fedml Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: fedml 0.9.6. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Fedml.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Fedml’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Fedml compares in Agent Frameworks

Bars show each HVTrust score; the tick marks Fedml’s 45.1.

Where the 45.1 comes from

HVTrust dimensions vs the Agent Frameworks average

45.1 / 100 · 100.0% confidence

Fedml Agent Frameworks average (130 agents)

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

6.9 / 25

3.0 below avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

11.9 / 17

0.5 below avg 12.4

Maintenance60% last-push freshness · 40% commit activity

0 / 20

14.4 below avg 14.4

AdoptionLog-scaled stars · package downloads

12.3 / 20

1.0 above avg 11.3

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-06

Rank Moved

Rank dropped 72 spots (#1043 → #1115)

2026-10-05

Rank Moved

Rank dropped 10 spots (#1033 → #1043)

2026-09-30

Rank Moved

Rank dropped 10 spots (#1015 → #1025)

Maintainer Checklist

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

Compare with another agent Get email alerts for Fedml View Agent Frameworks Report missing data

35.1

Activity sub-score · out of 100

#101

In Agent Frameworks

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

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars

4.1k

Forks

768

Last Push

2025-10-28

354 days ago

Commits (4 wk)

Downloads (7d)

508

pypi

HN mentions (30d)

—

Open Issues

122

Rank Change

was #1121

Analysis

Activity Inputs

35.1 / 100

StarsRepository reach

21.7 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

13.4 / 20

Common questions about Fedml

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

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

Does Fedml have an OpenSSF Scorecard?

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

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

What license does Fedml use?

Fedml ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Fedml's commits signed?

37% of the last 100 commits to Fedml 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: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

1 tags

Broad capability areas detected.

database

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Fedml?

For maintainers

HVTrust scores Fedml 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-10-06

Rank Moved

Rank dropped 72 spots (#1043 → #1115)

2026-10-05

Rank Moved

Rank dropped 10 spots (#1033 → #1043)

2026-09-30

Rank Moved

Rank dropped 10 spots (#1015 → #1025)

2026-09-25

Rank Moved

Rank dropped 11 spots (#1007 → #1018)

2026-09-23

Rank Moved

Rank dropped 614 spots (#399 → #1013)

2026-09-22

Rank Moved

Rank dropped 60 spots (#339 → #399)

2026-09-21

Rank Moved

Rank rose 673 spots (#1012 → #339)

2026-09-11

Rank Moved

Rank dropped 10 spots (#984 → #994)

2026-09-09

Rank Moved

Rank dropped 14 spots (#966 → #980)

2026-09-08

Rank Moved

Rank dropped 12 spots (#954 → #966)

2026-09-07

Rank Moved

Rank dropped 32 spots (#922 → #954)

2026-09-06

Rank Moved

Rank dropped 11 spots (#911 → #922)

2026-09-05

Rank Moved

Rank dropped 53 spots (#858 → #911)

2026-09-04

Rank Moved

Rank dropped 31 spots (#827 → #858)

2026-09-03

Rank Moved

Rank dropped 46 spots (#781 → #827)

2026-09-02

Rank Moved

Rank dropped 45 spots (#736 → #781)

2026-09-01

Rank Moved

Rank dropped 29 spots (#707 → #736)

2026-08-31

Rank Moved

Rank dropped 31 spots (#676 → #707)

2026-08-30

Rank Moved

Rank dropped 21 spots (#655 → #676)

2026-08-29

Rank Moved

Rank dropped 42 spots (#613 → #655)

2026-08-28

Rank Moved

Rank dropped 18 spots (#595 → #613)

2026-08-27

Rank Moved

Rank dropped 13 spots (#582 → #595)

2026-08-26

Rank Moved

Rank dropped 84 spots (#498 → #582)

2026-08-24

Rank Moved

Rank dropped 14 spots (#483 → #497)

2026-08-22

Rank Moved

Rank rose 13 spots (#500 → #487)

2026-08-19

Rank Moved

Rank dropped 12 spots (#490 → #502)

2026-08-17

Rank Moved

Rank rose 12 spots (#504 → #492)

2026-08-13

Rank Moved

Rank dropped 12 spots (#485 → #497)

2026-08-12

Rank Moved

Rank rose 10 spots (#495 → #485)

2026-08-10

Rank Moved

Rank dropped 16 spots (#479 → #495)

2026-08-08

Rank Moved

Rank dropped 125 spots (#351 → #476)

2026-07-29

Rank Moved

Rank dropped 12 spots (#334 → #346)

GitHub → Website → PyPI: fedml

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/fedml.svg)](https://hvtracker.net/agents/fedml)
            
HTML:
            <a href="https://hvtracker.net/agents/fedml"><img src="https://hvtracker.net/badge/fedml.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

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

Fedml

How Fedml could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Fedml compares in Agent Frameworks

Where the 45.1 comes from

HVTrust dimensions vs the Agent Frameworks average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Fedml

AI agent surface

Maintain Fedml?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Frameworks