Discofork
Repository brief

mermaid-js/mermaid

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-30T11:51:07.643Z
3mo ago

mermaid-js/mermaid

Mermaid is a large, active JavaScript/TypeScript monorepo for generating diagrams from markdown-like text, including flowcharts, sequence diagrams, class diagrams, gantt charts, and git graphs. It is widely used and heavily forked, with a large contributor and release workflow around docs, tests, and browser-based validation.

GitHub
Loading tags...
Stars86,974
Forks8,793
Default branchdevelop
Last pushed2026-03-30T05:02:04Z
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

10 of 10 fork briefs
Selected

Choose this fork only if you explicitly want to trim scheduled repo automation and can live with more manual upkeep. If you want the latest Mermaid fixes, CI checks, and maintenance workflows, upstream is the better default.

Choose this fork if draw.io integration or legacy UMD distribution matters more than staying current with upstream Mermaid. Choose upstream if you want the latest diagram features, fixes, and maintenance cadence.

Prefer upstream unless you specifically need a frozen old snapshot; this fork appears stale and offers no visible fork-only capabilities.

Prefer upstream unless you specifically need this older frozen state; adopters looking for current Mermaid features, fixes, and support should not choose this fork.

Prefer upstream unless you specifically need this fork's Cypress timing adjustments; it looks like a maintenance branch, not a feature-enhanced Mermaid distribution.

Prefer upstream unless you explicitly need this exact old snapshot. The fork adds no visible capabilities and is far behind on maintenance and features.

Prefer upstream Mermaid unless you explicitly need this old snapshot. This fork adds no visible value over upstream and is far behind, so adopters would mostly be buying maintenance risk.

Prefer upstream unless you specifically need this exact historical snapshot. For adopters, this fork offers no added capability and carries substantial maintenance and security risk because it is far behind current Mermaid.

Prefer upstream unless you specifically need this exact old snapshot. This fork adds no clear user-facing capabilities and is materially stale, so it is only attractive as a minimal legacy pin.

Prefer upstream unless you specifically need an old frozen Mermaid baseline; this fork appears inactive and materially outdated.