Discofork
Repository brief

pallets/flask

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-30T12:49:48.814Z
3mo ago

pallets/flask

Flask is a very popular, production-stable Python micro web framework for building WSGI web applications. It is actively maintained on the `main` branch, with a large ecosystem footprint (71,354 stars, 16,757 forks) and recent activity as of 2026-03-24.

GitHub
Loading tags...
Stars71,354
Forks16,757
Default branchmain
Last pushed2026-03-24T13:55:59Z
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 your goal is Chinese-localized Flask documentation. Do not choose it as a base for modern Flask application development or ongoing framework maintenance; it is too stale and too far behind upstream.

Choose this fork only if you need its historical asyncio/aiohttp direction or already depend on its old behavior. For new work, upstream Flask is the safer default because this fork is far behind and effectively unmaintained.

Choose upstream Flask unless you specifically need this old snapshot for compatibility. This fork adds no visible capabilities and is too far behind to be a good default for new work.

Choose this fork if your priority is Korean-localized documentation and you can tolerate a stale, heavily diverged codebase. Choose upstream if you need current Flask behavior, active maintenance, and lower integration risk.

Choose this fork only if you need its legacy/custom behavior and can absorb maintenance risk. For most new work, upstream Flask is the safer choice because this fork is materially stale and far behind current fixes and maintenance.

Prefer upstream Flask unless you specifically need this exact older snapshot; this fork adds no visible value and is materially behind current upstream.

Prefer this fork only for legacy Python 3.2 compatibility. For any new or actively maintained project, upstream Flask is the better choice because this fork is very stale and materially behind on features, tooling, and fixes.

Choose this fork only if Korean-translated Flask documentation is the primary value. For anything meant to run real applications or track modern Flask, upstream is the better choice.

Prefer upstream Flask unless you specifically need this fork's branding or frozen dependency files. This fork looks useful as a lightly customized snapshot, but its long lag makes it a poor adoption choice for anyone who wants current Flask behavior or maintenance.

Prefer upstream Flask unless you specifically need this fork's historical test snapshot; it adds no clear user-facing capability and is far behind current upstream.