updated 2026-10-09 08:15 UTC

Flyte

Repository Website

Type-safe, distributed orchestration of agents, ML pipelines, and real-time inference on your k8s — in pure Python with async/await, also other languages (rust, go and ts)

Workflow Platforms Go Listed Apache-2.0

Is Flyte safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.8 / 10
Provenance None
Signed commits 100%
Last push today
Advisories None known
Compare Flyte

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Flyte scores 71.9/100 (Grade B), ranked #305 of 1371 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 5.8/10; 100% of recent commits are signed; no published advisory affects its latest release (flytekit); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Flyte 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Flyte 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.

  1. Source Signed

    github.com/flyteorg/flyte, Apache-2.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.8/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 14 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CII-Best-Practices 5
    Code-Review 10
    Dangerous-Workflow 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0

  3. Published packages Not linked

    • PyPI flytekit Source link points to flyteorg/flytekit, same owner No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: flytekit 1.16.29. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-08-07 Provenance drift warning cleared (now: unknown)

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 Flyte’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 Flyte compares in Workflow Platforms

  1. #5 Dify 79.1 +7.2
  2. #6 Langflow 78.7 +6.8
  3. #7 Flyte 71.9 this agent
  4. #8 Hatchet 67.1 −4.8
  5. #9 Nocobase 66.0 −5.9

Bars show each HVTrust score; the tick marks Flyte’s 71.9.

Where the 71.9 comes from

HVTrust dimensions vs the Workflow Platforms average

71.9 / 100 · 100.0% confidence

Flyte Workflow Platforms average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.2 / 25
1.6 above avg 10.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
13.4 / 17
0.9 above avg 12.5
Maintenance60% last-push freshness · 40% commit activity
19.7 / 20
2.7 above avg 17.0
AdoptionLog-scaled stars · package downloads
16.1 / 20
3.3 above avg 12.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 172 spots (#108 → #280)
2026-09-21
Rank Moved
Rank rose 175 spots (#283 → #108)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/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.
Compare with n8n Get email alerts for Flyte View Workflow Platforms Report missing data
86.2
Activity sub-score · out of 100
#7
In Workflow Platforms

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
7.7k
Forks
900
Last Push
2026-10-09
today
Commits (4 wk)
86
Downloads (7d)
115,638
pypi
HN mentions (30d)
—
Open Issues
113
Rank Change
▼2
was #303

Analysis

Activity Inputs

86.2 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
24.2 / 25
CommunityFork signal
13.7 / 20

Common questions about Flyte

Flyte has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Flyte publish package provenance?
No published build provenance is currently detected for Flyte. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Flyte have an OpenSSF Scorecard?
Flyte has an OpenSSF Scorecard score of 5.8/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 Flyte actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Flyte use?
Flyte ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Flyte's commits signed?
100% of the last 100 commits to Flyte 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.

Compare Flyte head-to-head

Flyte vs n8n → Flyte vs Botpress → Flyte vs Trigger.dev →

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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Flyte'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
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)

Maintain Flyte?

For maintainers

HVTrust scores Flyte 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
Rank 8Drift 1
2026-09-23
Rank Moved
Rank dropped 172 spots (#108 → #280)
2026-09-21
Rank Moved
Rank rose 175 spots (#283 → #108)
2026-09-07
Rank Moved
Rank dropped 20 spots (#248 → #268)
2026-09-05
Rank Moved
Rank dropped 54 spots (#194 → #248)
2026-09-04
Rank Moved
Rank dropped 13 spots (#181 → #194)
2026-08-31
Rank Moved
Rank dropped 18 spots (#146 → #164)
2026-08-26
Rank Moved
Rank dropped 15 spots (#120 → #135)
2026-08-07
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-07-13
Rank Moved
Rank dropped 14 spots (#114 → #128)
GitHub → Website → PyPI: flytekit

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 71.9 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/flyte.svg)](https://hvtracker.net/agents/flyte)
HTML:
<a href="https://hvtracker.net/agents/flyte"><img src="https://hvtracker.net/badge/flyte.svg" alt="HVTrust"></a>

Other agents in Workflow Platforms

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