/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

trekhleb/javascript-algorithms

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-29T22:02:52.805Z

3mo ago

trekhleb/javascript-algorithms

A large Node.js/JavaScript repository of algorithms and data structures with per-topic explanations, examples, and further-reading links. It is highly popular and actively maintained, with very high fork and star counts and recent commits as of 2026-02-18.

Loading tags...

Stars195,761

Forks31,099

Default branchmaster

Last pushed2026-02-18T09:20:06Z

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

6 of 6 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you want its older, customized state and are prepared to maintain it yourself. If you want a current algorithms reference library with active upkeep, upstream is the better choice.

Prefer upstream unless you specifically want a static snapshot; this fork adds no visible capabilities and is materially behind on fixes, content, and toolchain updates.

Prefer upstream for almost any active use. Choose this fork only if you specifically want an older frozen copy and do not need the newer fixes, dependency upgrades, or added explanations present upstream.

Choose this fork only if you want a frozen, historically interesting algorithms reference with extra example material. If you want current maintenance, latest fixes, and ongoing compatibility, upstream is the better default.

Prefer upstream unless you specifically need the fork’s custom additions and are willing to absorb a stale, heavily diverged codebase. This fork is best viewed as an archived customization branch, not the default choice for new adopters.

Prefer upstream unless you specifically want a mostly unchanged historical snapshot. This fork offers no clear functional expansion, while its long inactivity and 102-commit lag make it a weak choice for adopters who want current fixes or ongoing maintenance.

Fork comparison

gopinav/javascript-algorithms

38/100

stale

significant_divergence

Prefer this fork only if you want its older, customized state and are prepared to maintain it yourself. If you want a current algorithms reference library with active upkeep, upstream is the better choice.

Likely purpose

To preserve or customize an older version of the project for educational use, likely with a different documentation set and local algorithm/test experiments rather than to track upstream closely.

Best for

Learners who specifically want an older, customized snapshot of the algorithms project.; Maintainers who plan to own the fork long-term and do not need upstream parity.; Users interested in a fork centered on algorithm explanations plus local experiments in image processing or cryptography.

Additional features

Adds or reshapes content around image-processing algorithms, including seam carving.
Touches cryptography algorithm areas, suggesting broader algorithm coverage or reorganization beyond the original core topics.
Includes substantial test updates in matrix and red-black tree areas, which may improve local correctness coverage for maintainers or learners.
Reworks README content and translations, indicating a documentation-focused fork experience.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

Falls far behind upstream, so it likely misses many years of new algorithms, fixes, and documentation improvements.
Does not track upstream's newer Node.js 22 / npm 10 baseline and dependency upgrades.
Several translated README files were deleted or reduced, so multilingual documentation is weaker than upstream.
Recent upstream CI and maintenance changes are absent, making it harder to adopt as a current drop-in replacement.
It trails upstream by 203 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Could be useful if you want a frozen, older snapshot with custom local edits.
May suit teams or learners who prefer a fork that emphasizes specific algorithm topics and custom tests.
Large diff suggests the fork is not just a shallow mirror; it reflects intentional curation and divergence.

Risks

High divergence makes upstream merges difficult.
The repository is very stale, so security, compatibility, and correctness risk is higher.
Documentation and translation deletions may reduce accessibility for non-English readers.
As an older fork, it is a poor choice if you want current package, runtime, or CI behavior.

trekhleb/javascript-algorithms · Discofork