/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

labmlai/annotated_deep_learning_paper_implementations

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-30T13:05:17.962Z

3mo ago

labmlai/annotated_deep_learning_paper_implementations

Large, actively maintained PyTorch repository of 60+ deep learning paper implementations with side-by-side explanatory notes and a companion documentation site. It is broad in scope, covering transformers, diffusion, GANs, RL, optimizers, and related models, and is widely forked and starred. Forks are most interesting if you want readable reference implementations plus documentation rather than a single-purpose library.

Loading tags...

Stars66,191

Forks6,657

Default branchmaster

Last pushed2026-01-22T04:26:00Z

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

Maintenance:

Magnitude:

Sort:

Selected

Choose the upstream repo unless you specifically want an essentially unmodified, stale copy. This fork offers little adopter value beyond mirroring upstream and is behind by 31 commits.

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

Choose upstream unless you specifically want a static August 2024 snapshot; this fork adds no visible capabilities and is materially behind current upstream maintenance.

Prefer this fork only if you specifically want a frozen copy from 2022. For any active use, the upstream project is the better choice because this fork has no unique changes and is far behind upstream.

Choose upstream if you want the broad, current, fully maintained tutorial repository. Choose this fork only if you specifically want an older, trimmed snapshot and are comfortable losing newer coverage and multilingual docs.

Prefer upstream unless you specifically want a frozen 2022 snapshot. This fork adds no visible capabilities, is far behind upstream, and looks unsuitable for active adoption.

Prefer this fork only if the added audio quickstart is exactly the workflow you want. Otherwise, upstream is the better default because this fork is nearly identical, much older, and unlikely to stay current.

Prefer upstream unless you specifically want a frozen snapshot. This fork does not add visible capabilities, and it is materially behind upstream, so it is weaker for anyone who wants current implementations or active maintenance.

Prefer upstream unless you specifically need this old snapshot. This fork adds no visible capabilities, while missing a substantial amount of later upstream work.

Prefer upstream unless you explicitly need this older snapshot; the fork adds no new capabilities and is materially behind current upstream.

Fork comparison

eust-w/annotated_deep_learning_paper_implementations

35/100

stale

minor

Choose the upstream repo unless you specifically want an essentially unmodified, stale copy. This fork offers little adopter value beyond mirroring upstream and is behind by 31 commits.

Likely purpose

To keep a personal or team copy of the upstream reference repo without diverging from it.

Best for

Users who want a frozen copy of the upstream repository for reference or archival purposes.; Teams that prefer minimal divergence and plan to track upstream manually.; Learners who only need the existing annotated implementations and do not need active fork maintenance.

Additional features

Missing features

No fork-specific enhancements beyond upstream are visible in this comparison.
It is 31 commits behind upstream, so it likely misses newer paper implementations, documentation updates, and bugfixes.
Because there are no local changes, it does not add new workflows, platforms, or APIs that downstream adopters could rely on.
It trails upstream by 31 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Still inherits the upstream repo's broad, readable PyTorch paper-implementation library.
Good fit if you want the upstream codebase with minimal divergence.
Low integration risk because the fork has not introduced custom modifications.

Risks

Staleness means upstream improvements are absent.
Adopters cannot expect fork-specific maintenance or feature additions from this snapshot.
If you need the newest tutorials or fixes, this fork is not a better choice than upstream.