Is Flyte safe to use?

Flyte has an HVTrust score of 72.3/100 (Grade B), ranked #114 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Flyte?

Flyte scores 72.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 7.2k GitHub stars and is categorized under Workflow Platforms.

Flyte

flyteorg/flyte

Dynamic, resilient AI orchestration. Coordinate data, models, and compute as you build AI workflows.

Workflow Platforms Go Grade B Listed Apache-2.0

72.3/100

Rank #114 of 1283

Compare Flyte

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 0d ago

Recent change

Drift Warning Cleared

Is Flyte safe? Flyte scores 72.3/100 (Grade B), ranked #114 of 1283 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.9/10; 100% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Workflow Platforms

#5 Dify — 79.1 (B) → #6 Flowise — 75.2 (B) → #8 Airbyte — 67.1 (B) → #9 Nocobase — 66.4 (B) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-07

Drift Warning Cleared

Provenance drift warning cleared (now: unknown)

2026-07-13

Rank Moved

Rank dropped 14 spots (#114 → #128)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.9/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 Trigger.dev Get email alerts for Flyte View Workflow Platforms Report missing data

86.8

Activity sub-score · out of 100

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 →

Activity & Reach

Stars

7.2k

Forks

868

Last Push

2026-08-11

today

Commits (4 wk)

118

Downloads (7d)

98,218

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #113

Analysis

HVTrust Dimensions vs Workflow Platforms

72.3 / 100 · 100.0% confidence

Flyte Workflow Platforms average (24 agents)

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

12.4 / 25

2.0 above avg 10.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

13.5 / 17

1.1 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

1.8 above avg 18.2

AdoptionLog-scaled stars · package downloads

15.9 / 20

3.0 above avg 12.9

Activity Inputs

86.8 / 100

StarsRepository reach

23.1 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

13.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.9 / 10

OpenSSF Scorecard · scanned Aug 10, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 5

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Flyte safe?

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.9/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 Trigger.dev → Flyte vs n8n → Flyte vs Botpress →

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)

2026-06-05

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

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

2026-08-07

Drift Warning Cleared

Provenance drift warning cleared (now: unknown)

2026-07-13

Rank Moved

Rank dropped 14 spots (#114 → #128)

2026-07-08

Grade Changed

Trust grade C → B

2026-07-08

Rank Moved

Rank rose 12 spots (#118 → #106)

2026-06-05

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-05-29

HVTrust Changed

HVTrust up 9.9pts (56.6 → 66.5)

2026-05-28

Activity Score Changed

Activity score up 23pts (62 → 85)

2026-05-25

Rank Moved

Rank dropped 33 spots (#64 → #97)

2026-05-24

Newly Listed

First tracked at rank #64

GitHub → PyPI: flytekit

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON