Discofork
Repository brief

penpot/penpot

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:38:19.834Z
3mo ago

penpot/penpot

Penpot/penpot is a large, active open-source design tool repository with 45,105 stars and 2,636 forks. It targets browser-based or self-hosted design/code collaboration, includes plugins, design tokens, and a sizable multi-part codebase. Recent commits on 2026-03-30 show active maintenance across frontend, backend, and tooling.

GitHub
Loading tags...
Stars45,105
Forks2,636
Default branchdevelop
Last pushed2026-03-30T11:35:27Z
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

Prefer upstream unless you specifically need this fork's custom rendering/plugin/MCP changes and are prepared to own a large maintenance burden. For most adopters, the stale state and extreme divergence make this a risky base to start from.

Prefer this fork only if you need its specific developer/runtime changes and are prepared to maintain a large upstream gap. For most adopters, upstream Penpot is the safer choice because it is far more current and actively maintained.

Prefer upstream unless you specifically need a frozen, unmodified snapshot. This fork adds no visible capabilities and is substantially behind on maintenance, so it is only attractive for narrow pinning or experimentation use cases.

Choose upstream unless you specifically need this exact older snapshot. This fork does not add visible capabilities and is materially behind an actively maintained Penpot upstream, so it is a poor adoption target for most users.

Prefer this fork only if you need its custom workflow or API/runtime direction and are willing to maintain it yourself. For most users, upstream Penpot is the safer choice because this fork is materially stale and heavily diverged.

Prefer this fork only if you specifically need its legacy behavior or fork-specific component fixes. For most adopters, current upstream Penpot is the safer choice because this fork is stale, heavily diverged, and likely missing major recent product work.

Prefer this fork only if you specifically need an older Penpot snapshot with a few targeted tweaks; otherwise upstream is the better choice because it is far more current, actively maintained, and likely richer in features and fixes.

Choose this fork only if you need the historical UXBOX-era code. For nearly everyone else, upstream Penpot is the better choice because this fork is severely outdated and materially behind on product, workflow, and maintenance.

Choose this fork only if you want a near-stock Penpot snapshot; otherwise upstream is the better default because this fork adds no visible functionality and is behind current upstream.

Prefer upstream unless you specifically want to build your own fork from an older baseline. This fork adds no visible value on its own and is materially behind upstream, so adopters should expect to spend time catching up before using it seriously.