TheAlgorithms/JavaScript
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
TheAlgorithms/JavaScript
Large, active educational repository of JavaScript implementations of algorithms and data structures. It is popular (34k stars, 5.8k forks), not archived, and appears maintained with recent commits through 2026-03-07. Forks are most interesting if you want a broad, beginner-friendly algorithm catalog with tests and contributing workflow already in place.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Choose this fork only if you want a mostly unchanged copy of upstream for your own experimentation. If you want an actively maintained algorithm library, upstream is the better choice.
Prefer upstream unless you specifically want a static snapshot; this fork adds no visible capability and is already lagging behind recent upstream fixes and additions.
Prefer upstream unless you specifically need this stale snapshot. This fork offers no added capability and is behind on upstream fixes and improvements.
Choose upstream unless you specifically need a frozen June 2024 snapshot; this fork adds no visible capabilities and is materially behind on active maintenance.
Prefer upstream unless you explicitly want an older frozen copy. This fork adds no visible capabilities and is materially behind on maintenance.
Prefer upstream unless you specifically need this fork’s namespace or want to build your own derivative from a frozen snapshot. For most adopters, the fork adds no visible value and is behind current upstream activity.
Prefer upstream unless you specifically need this exact older snapshot; this fork adds no visible value and is materially behind.
Choose the upstream repository if you want the broadest, most current, and best-maintained algorithm catalog. Choose this fork only if you specifically want its older, heavily rewritten snapshot and are comfortable carrying the maintenance burden yourself.
Choose this fork only if you want an almost exact copy of upstream. If you want active evolution, extra features, or maintained divergence, upstream is the better default.