updated 2026-10-09 08:15 UTC

Dify

Repository Website

Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.

Workflow Platforms TypeScript Listed NOASSERTION Source-available

Is Dify safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.2 / 10
Provenance None
Signed commits 100%
Last push today
Compare Dify

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Dify scores 79.1/100 (Grade B), ranked #172 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.2/10; 100% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

What Dify can reach, and who runs it

Checked 2026-10-06, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves. These facts describe the product. They don't change its score.

Who runs it

  • PUBLISHER Run by LangGenius, Inc., a Delaware corporation. dify.ai

Security practice

  • PUBLISHER States SOC 2 Type II (audited by Sensiba), ISO 27001:2022 (Johanson) and GDPR compliance, as of March 2026. dify.ai
  • CHECKED Its maintainers have published 21 security advisories (8 high, 10 medium, 3 low), 14 of them in the last 12 months. github.com
  • CHECKED The repository has a SECURITY.md and GitHub private vulnerability reporting is enabled. dify.ai serves no security.txt. github.com
Something wrong or out of date? Suggest a correction

How Dify 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 Dify 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/langgenius/dify, NOASSERTION, 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 6.2/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection1
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies7
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 9
    Maintained 10
    Packaging 10
    Pinned-Dependencies 7
    SAST 7
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm dify Source link isn't a GitHub repo No build attestation
    • PyPI dify-client Source link points back to this repo No build attestation

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

Changes to this chain

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

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Dify’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 Dify compares in Workflow Platforms

  1. #3 Trigger.dev 86.7 +7.6
  2. #4 Hypit 82.1 +3.0
  3. #5 Dify 79.1 this agent
  4. #6 Langflow 78.7 −0.4
  5. #7 Flyte 71.9 −7.2

Bars show each HVTrust score; the tick marks Dify’s 79.1.

Where the 79.1 comes from

HVTrust dimensions vs the Workflow Platforms average

79.1 / 100 · 100.0% confidence

Dify Workflow Platforms average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.8 / 25
2.2 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.8 / 17
1.3 above avg 12.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
3.0 above avg 17.0
AdoptionLog-scaled stars · package downloads
20.0 / 20
7.2 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 73 spots (#74 → #147)
2026-09-21
Rank Moved
Rank rose 88 spots (#161 → #73)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/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 Dify View Workflow Platforms Report missing data
100.0
Activity sub-score · out of 100
#5
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 A is separate — it grades how many independent signal types back the score (4 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
158.0k
Forks
24.9k
Last Push
2026-10-09
today
Commits (4 wk)
705
Downloads (7d)
24,521,643
docker+pypi
HN mentions (30d)
479
Open Issues
472
Rank Change
▼1
was #171

Analysis

Activity Inputs

100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Common questions about Dify

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Dify may have internal security practices not visible through public signals.
Public supply-chain signals for Dify are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Dify carries less obvious unverified-evidence risk than projects with thin signals.
Does Dify publish package provenance?
No published build provenance is currently detected for Dify. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Dify have an OpenSSF Scorecard?
Dify has an OpenSSF Scorecard score of 6.2/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 Dify actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Dify use?
Dify ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Dify's commits signed?
100% of the last 100 commits to Dify 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 Dify head-to-head

Dify vs n8n → Dify vs Botpress → Dify 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
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
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
medium confidence
Partial
Some package metadata matches; some source metadata is missing
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Dify?

For maintainers

HVTrust scores Dify 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 5
2026-09-23
Rank Moved
Rank dropped 73 spots (#74 → #147)
2026-09-21
Rank Moved
Rank rose 88 spots (#161 → #73)
2026-09-07
Rank Moved
Rank dropped 12 spots (#140 → #152)
2026-09-05
Rank Moved
Rank dropped 30 spots (#111 → #141)
2026-08-31
Rank Moved
Rank dropped 13 spots (#90 → #103)
GitHub → Website → PyPI: dify-client npm: dify

Embed Badge Badge guide for maintainers →

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

Other agents in Workflow Platforms

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