Discofork
Repository brief

mingrammer/diagrams

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-31T10:15:58.043Z
1mo ago

mingrammer/diagrams

mingrammer/diagrams is an active Python project for drawing cloud system architecture diagrams as code. It is popular and well-maintained, with 42k+ stars, 2.7k+ forks, a recent push on 2026-03-30, and ongoing feature work. For fork interest, it looks most relevant if you care about extending diagram providers, styling, or diagram-generation workflows rather than cloud infrastructure management itself.

GitHub
Loading tags...
Stars42,135
Forks2,725
Default branchmaster
Last pushed2026-03-30T19:49:31Z
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 if you value the extra icon/path/layout tweaks more than staying close to upstream. Choose upstream if you want the newest features, styling, and lower maintenance burden.

Prefer this fork only if SAP coverage is the main requirement. For general diagrams-as-code use, upstream is the better default because it is newer, more active, and has broader recent feature work.

Choose this fork only if Open Telekom Cloud support is the main requirement. For general diagrams-as-code use, upstream is the safer default because it is much more active and feature-rich.

Choose upstream unless you specifically need the custom icon argument change; this fork looks like a tiny, stale customization layer with substantial upstream drift.

Choose the fork only if you explicitly want an older, diverged snapshot and are prepared to maintain it yourself. For most adopters, upstream is the better choice because it is active, newer, and has substantially more recent feature and maintenance work.

Prefer upstream unless you specifically need this fork's older customized state. Adopt this fork only if its local changes are already the desired product and you are prepared to own the maintenance gap.

Choose this fork if OpenTelekomCloud support is the main requirement. Choose upstream if you want the most current diagrams feature set, broader maintenance, and newer provider/styling work.

Prefer upstream unless you specifically want an old, frozen baseline. This fork adds no visible capabilities and is materially behind on features and maintenance.

Choose this fork only if you specifically need its older custom styling/layout behavior. For most adopters, upstream is the better default because this fork is very stale and materially behind on features, fixes, and provider coverage.

Choose this fork if you specifically want AWS CloudFormation-oriented diagram support while staying close to upstream. If you want the newest upstream styling and fixes first, the main project is the safer default.