Repository brief

n8n-io/n8n

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-29T22:05:42.219Z

n8n-io/n8n

n8n is a large, actively maintained workflow automation platform with native AI features, 400+ integrations, and both self-hosted and cloud deployment options. It is source-available under fair-code licenses rather than a standard permissive OSS license. The repo is very active, with recent commits on March 27-29, 2026, and a large community footprint (181,619 stars, 56,283 forks).

GitHub

Stars181,619

Forks56,283

Default branchmaster

Last pushed2026-03-29T15:11:10Z

Best maintaineddeluxebear/n8n

Closest to upstreamguillaumegay13/n8n-agentic

Most feature-richdevszilla/n8n-puppeteer

Most opinionateddevszilla/n8n-puppeteer

Forks

Choose a fork to inspect

6 cached fork briefs

Fork comparison

deluxebear/n8n

active

significant_divergence

Choose this fork if you value Chinese localization and custom assistant-oriented workflows more than strict upstream parity. Avoid it if you need the safest path to upstream compatibility, because the fork is materially diverged and still trailing upstream changes.

Likely purpose

For adopters who want n8n’s core workflow platform but prefer a fork that is actively updated, localized for Chinese users, and customized for repo-specific AI assistant and workflow behavior.

Best for

Chinese-speaking technical teams who want a localized n8n experience.; Power users who want an actively maintained fork with custom assistant/workflow tooling.; Teams willing to trade upstream parity for fork-specific customization.; Organizations that can validate changes internally and absorb divergence risk.

Additional features

Large Chinese localization coverage (`zh-CN.json` is heavily expanded).
Repo-integrated Claude/plugin/skill workflows under `.claude/` and `.agents/` for assistant-driven maintenance and automation.
Customizations in workflow and node behavior, including substantial edits around Jira, Zammad, MCP, and agent-related code paths.
Custom developer/release workflow support visible in fork-specific repo structure and automation files.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.

Missing features

The fork is about 200 commits behind upstream, so some recent upstream fixes and features are not yet included.
Large deletions in agent-runtime, MCP tests, and other test files suggest reduced parity or lower confidence in some AI/agent and tooling workflows versus upstream.
The scope of rewrites makes upstream behavior harder to assume stable; adopters may need to verify node, agent, and editor flows before relying on them.
Upstream release cadence is very active, so this fork may lag on fast-moving platform and integration changes even while it keeps rebasing.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Recently pushed and still active.
Very large upstream base with broad integration coverage retained.
Likely better fit for Chinese-speaking teams and users who want localized UX.
Appears tuned for advanced automation and assistant-assisted development workflows.

Risks

High divergence increases merge/rebase risk and makes upstream documentation less reliable.
Removed or rewritten tests raise regression risk.
Behavioral differences may surface in AI agent, MCP, and integration nodes.
Adoption is riskier if you need strict upstream compatibility or predictable release parity.