/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

rust-lang/rustlings

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:22.362Z

3mo ago

rust-lang/rustlings

Rustlings is a popular Rust learning repository with small coding exercises, supporting a companion website and solution/test infrastructure. It looks actively maintained, with recent commits in March 2026, and is a strong fork target if you want to customize Rust onboarding, curriculum, or the exercise runner.

Loading tags...

Stars62,320

Forks11,170

Default branchmain

Last pushed2026-03-25T17:30:03Z

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

Prefer this fork if you want a customized Rustlings solutions codebase and are willing to own divergence; prefer upstream if you want the current, actively maintained project with the latest fixes and tooling.

Choose this fork only if its custom exercise/runtime behavior is the point. For most adopters, upstream is the safer default because this fork is old, far behind, and likely missing many recent fixes and maintenance updates.

Prefer this fork if your goal is ZK education, not general Rust onboarding. Prefer upstream Rustlings if you want the broader, better-maintained, more current exercise set and infrastructure.

Choose this fork if you want Rustlings as a solutions/reference repository. Do not choose it if you want the latest upstream learning experience, because it is materially behind and optimized around completed answers rather than the standard exercise flow.

Prefer this fork only if you specifically want its customized curriculum and are willing to maintain it yourself. If you want an actively maintained Rustlings base, upstream is the safer choice.

Prefer this fork if you want a solution-heavy Rustlings teaching fork. Prefer upstream if you want current maintenance, cleaner upgrade paths, and the latest exercise/tooling behavior.

Prefer the fork only if you specifically want a historical solutions mirror; prefer upstream for any current learning, teaching, or maintenance use.

Prefer this fork only if you specifically want solutions for the 2020-era Rustlings set. If you want current Rustlings content, tooling, or a maintained learning repo, upstream is the better choice.

Prefer this fork only if you specifically want a solved, customized Rustlings copy. If you want an actively maintained learning repo, upstream is the better choice.

Choose this fork only if you want its customized training content or repo workflow as-is. Choose upstream if you want active maintenance, current fixes, and lower long-term maintenance cost.

Fork comparison

wh5a/rustlings-solutions

54/100

slowing

significant_divergence

Prefer this fork if you want a customized Rustlings solutions codebase and are willing to own divergence; prefer upstream if you want the current, actively maintained project with the latest fixes and tooling.

Likely purpose

Provide a maintained Rustlings solutions fork for users who want a curated, customized training/codebase rather than the upstream project as-is.

Best for

Instructors who want a Rustlings-derived solutions fork to distribute or adapt.; Maintainers who prefer a customized training repo over a clean upstream mirror.; Users who care more about having a solved, localized baseline than staying current with upstream Rustlings.

Additional features

Updated solutions across many exercises and support files.
Custom contributor/authorship metadata and repository information management.
Reworked core CLI/app state and exercise handling, suggesting tailored local workflows for running or verifying solutions.
Modified dev and test infrastructure to fit the fork's own maintenance process.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

Lagging behind upstream by 427 commits, so recent upstream fixes, CI updates, dependency bumps, and tooling changes are not present here.
Core upstream internals appear rewritten or removed in places such as app state, list state, terminal handling, and dev check code, which may make this a poorer drop-in replacement.
The fork is stale relative to its own last push date in 2024, so ongoing upstream compatibility is likely weaker.
It trails upstream by 427 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Large amount of solution-oriented content already incorporated.
Substantial customization of the learning and verification flow.
Could be useful as a starting point for instructors or maintainers who want a forked Rustlings baseline instead of the upstream repository.

Risks

High divergence raises merge and maintenance cost.
Being behind upstream means security, tooling, and exercise updates may be missing.
The repo looks inactive, so adopters should expect to carry maintenance themselves.