/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

langchain-ai/langchain

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T07:38:39.549Z

3mo ago

langchain-ai/langchain

LangChain is a very active, widely used Python framework for building agents and LLM-powered applications. The repo is the main upstream for the agent engineering platform, with a large ecosystem focus and frequent recent releases/fixes.

Loading tags...

Stars131,573

Forks21,685

Default branchmaster

Last pushed2026-03-30T00:54:07Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

4 of 4 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if you want a Russian-oriented LangChain distribution with GigaChat and example-driven workflows. Choose upstream if you need the newest LangChain features, broad provider coverage, and the lowest integration risk.

Prefer this fork only if you specifically need its older custom integrations and are comfortable owning the upgrade burden. For new work or active maintenance, upstream LangChain is the safer choice.

Prefer this fork only if you need a frozen, heavily customized LangChain baseline and are willing to maintain it yourself. If you want current provider support, ecosystem compatibility, and low merge debt, upstream is the better choice.

Choose this fork only if you need an older, customized LangChain baseline and are willing to own maintenance. If you want current provider support, bugfixes, and ecosystem compatibility, upstream is the better choice.

Fork comparison

ai-forever/gigachain

54/100

slowing

significant_divergence

Choose this fork if you want a Russian-oriented LangChain distribution with GigaChat and example-driven workflows. Choose upstream if you need the newest LangChain features, broad provider coverage, and the lowest integration risk.

Likely purpose

Serve teams that want a LangChain-based framework tailored to Russian-language workflows and GigaChat-first development, rather than tracking upstream LangChain closely.

Best for

Russian-speaking developers building LLM apps with GigaChat.; Teams that want LangChain concepts and examples adapted for local usage.; Users who prefer a downstream fork with opinionated examples over strict upstream parity.; Projects that value localization more than immediate access to every upstream release.

Additional features

Russian-language positioning and documentation for LLM app development.
GigaChat-focused support and examples, including `giga_agent` and related cookbook material.
Extra example workflows such as tagme and lean-canvas style agent demos.
Fork-specific doc and import adjustments aimed at making the stack easier to use in this downstream.
Localized development materials for users building Russian-language agent applications.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

Falls behind upstream by about 200 commits, so it likely misses recent LangChain fixes and provider updates.
Upstream’s latest changes in OpenAI, Anthropic, OpenRouter, Hugging Face, text splitters, and core agent behavior are not yet present here.
Appears to be much less current with the fast-moving LangChain ecosystem, which increases compatibility risk for adopters who need the newest integrations and bug fixes.
The fork looks harder to treat as a drop-in upstream replacement because of the large divergence and heavy deletions in the diff.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Better fit for Russian-speaking teams.
Likely smoother path for GigaChat-centric projects.
Includes practical agent/application examples rather than only core framework code.
Recent push history suggests it is still maintained enough for active use.

Risks

Large divergence from upstream makes future merges and upgrades harder.
Lagging upstream can leave users without recent bug fixes and provider compatibility work.
Heavy deletions suggest some upstream functionality may have been removed or made less accessible.
Adopters may need to validate compatibility before relying on newer LangChain APIs.

langchain-ai/langchain · Discofork