Discofork
Repository brief

encode/django-rest-framework

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-30T19:54:11.456Z
1mo ago

encode/django-rest-framework

encode/django-rest-framework is a mature, actively maintained Python package for building web APIs with Django. It is widely used, with 29,940 stars and 7,074 forks, and it was updated most recently on 2026-03-30. The repository shows ongoing release work and recent bug fixes, including a 3.17.1 release prep commit.

GitHub
Loading tags...
Stars29,940
Forks7,074
Default branchmain
Last pushed2026-03-29T09:57:51Z
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 specifically need its older CoreAPI/legacy snapshot and are comfortable owning maintenance. For most adopters, upstream is the better default because it is actively maintained and materially newer.

Prefer the upstream project unless you specifically need this older snapshot for compatibility. This fork adds no visible capabilities and is materially behind on fixes and maintenance, so it is a poor choice for new adopters seeking current DRF behavior.

Choose upstream unless you specifically need this older snapshot; the fork shows no added functionality and is materially behind current DRF.

Prefer upstream unless you specifically need the fork's legacy/custom schema and documentation behavior. This fork looks like a specialized, stale downstream branch rather than a safer or more current DRF distribution.

Prefer upstream unless you already depend on this fork's legacy documentation/schema customizations; the fork is stale and far behind current DRF, so it is best treated as a legacy snapshot rather than a healthy alternative.

Prefer the upstream project unless you specifically need this fork's historical customizations and are prepared to maintain a large, stale divergence yourself. This fork is best treated as a legacy codebase, not a modern starting point.

Choose this fork only if you need its legacy custom behavior and are prepared to maintain it yourself. For new work or active projects, upstream DRF is the safer choice.

Prefer upstream unless you specifically need this exact snapshot; this fork adds no new capability and is behind on recent fixes.

Choose this fork only if you specifically need the older CoreAPI-era behavior or the bundled legacy docs/assets. For new work or active maintenance, upstream is the better choice because it is much more current and actively maintained, while this fork is heavily stale and structurally behind.

Prefer upstream unless you specifically need this fork’s older CoreAPI/doc customizations and are prepared to maintain a stale, highly divergent codebase yourself.