Is Dify safe?
Dify scores 76.4/100 (Grade B), ranked #54 of 328 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.0/10;
100% of recent commits are signed;
last pushed 2026-07-10. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
76.4/100 · Grade B
Strongest Signal
Adoption
20.0/20
Weakest Signal
Safety / Integrity
12.5/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 6.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
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 refreshed2026-07-11 04:00 UTC·Repo last pushed yesterday
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
148.4k
Forks
23.4k
Last Push
2026-07-10
yesterday
Commits (4 wk)
555
Downloads (7d)
19,857,567
npm+docker+pypi
HN mentions (30d)
479
Open Issues
274
Rank Change
=
was #54
Analysis
HVTrust Dimensions
76.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.6 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
20.0 / 20
Activity Inputs
100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.0 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection1
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License9
Maintained10
Packaging10
Pinned-Dependencies6
SAST5
Security-Policy10
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is Dify safe?
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.0/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.
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.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Marketplace
Marketplace plugin/integration surface detected.
browser
code
search
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
How this surface has changed
Detected changes to Dify'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.
Runtime surface grew — new detected provider dependencies: OpenAI, Postgres
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → declared
Maintain Dify?
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.
