langgenius/dify
First read
Visible and active, but adoption proof is still thinner
langgenius/dify has enough public attention and recent movement to stay on the shortlist, but package usage is still partial, so the next step should be source and ecosystem validation rather than a quick yes.
134.8K public stars in the current GitStar snapshot.
Long-term anchor
Last commit Mar 28, 2026.
Fresh activity
Treat stars as discovery context until a linked package appears.
No linked package mapping
One or more key signals are partial, so GitStar keeps the interpretation conservative.
Partial snapshot
Snapshot facts
- 134.8K stars
- 21K forks
- Last commit Mar 28, 2026
- Package usage not mapped yet
Compare lens
n8n-io/n8n and langchain-ai/langchain are the closest comparison targets GitStar found. A side-by-side comparison usually tells you more than a single raw rank.
Signal trail
Trajectory
Read the recent motion first. This block is for deciding whether the repository still looks alive, compounding, or flattening before you trust stars alone.
Package reality
No linked npm or PyPI package is mapped for this repository yet, so the page leans more heavily on GitHub-visible popularity and should be read more conservatively.
GitStar expects a package signal here, but no npm or PyPI package is linked to this repository yet.
Validation note
GitStar can summarize public signals for langgenius/dify, but the GitHub repository is still the primary place to confirm release cadence, issue activity, and maintainer intent.
GitStar surfaces public popularity and package signals. These rankings are not endorsements, security reviews, or investment advice.
Why this rank
This repository stands out because it combines 100 daily momentum and fresh update.
Reconstructed from current stars and cached daily/weekly/monthly deltas.
GitStar can see repository momentum, but it does not have a reliable linked package signal yet.
Treat stars and recent movement as discovery context only until npm or PyPI usage is available.
n8n-io/n8n
Shares the frameworks category footprint with langgenius/dify, so the comparison is closer to a same-problem decision than a same-language coincidence.
langchain-ai/langchain
Shares the frameworks category footprint with langgenius/dify, so the comparison is closer to a same-problem decision than a same-language coincidence.
huggingface/transformers
Shares the frameworks category footprint with langgenius/dify, so the comparison is closer to a same-problem decision than a same-language coincidence.
shadcn-ui/ui
Shares the frameworks category footprint with langgenius/dify, so the comparison is closer to a same-problem decision than a same-language coincidence.
Cross-links
GitStar picked n8n + langchain as the closest next comparison from the related repository set.
Embed Badge
[](https://gitstar.space/repo/langgenius/dify)<a href="https://gitstar.space/repo/langgenius/dify"><img src="https://gitstar.space/api/badge/langgenius/dify" alt="GitStar"></a>🔗 Wider nearby ecosystem
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
The agent engineering platform
🤗 Transformers: the model-definition framework for state-of-the-art machine learning models in text, vision, audio, and multimodal models, for both inference and training.
A set of beautifully-designed, accessible components and a code distribution platform. Works with your favorite frameworks. Open Source. Open Code.
An opinionated list of Python frameworks, libraries, tools, and resources.
An Open Source Machine Learning Framework for Everyone
Next step after the validation read
Learn and methodology
About This Page
This page provides a quick overview of langgenius/dify based on GitStar's cached data. The signal chart reconstructs approximate checkpoints from current stars plus cached daily, weekly, and monthly star deltas, so it is best read as directional context rather than as a precise historical audit log.
Want to show your project's ranking? Copy the badge embed code above and add it to your README.