/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

facebook/folly

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:55:47.394Z

1mo ago

facebook/folly

`facebook/folly` is a large, actively maintained open-source C++20 library from Facebook/Meta, focused on practical, high-performance components used across its own open-source C++ projects. It has substantial adoption signals in the repo metadata, with 30k+ stars and 5.8k+ forks, and recent commits show ongoing work as of 2026-03-30.

Loading tags...

Stars30,309

Forks5,857

Default branchmain

Last pushed2026-03-30T18:48:36Z

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

9 of 9 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer upstream unless you specifically need this old snapshot’s local patches; this fork is too stale and divergent for most new adopters.

Choose this fork only if you need its exact historical snapshot or its local patches; for most adopters, upstream folly is the safer and more maintainable base.

Prefer this fork only if you need its older, customized behavior and are willing to own long-term maintenance. For most adopters, upstream folly is the better choice because this fork is materially behind and substantially diverged.

Prefer upstream unless you specifically need this branch's legacy behavior or downstream customizations. This fork is not a good choice for teams that want current support, low maintenance, or close alignment with Folly's ongoing development.

Choose this fork only if you need its older baseline and local tweaks; for most adopters, upstream Folly is the better default because this fork is materially stale and heavily diverged.

Choose this fork only if you need its older, customized Folly behavior and can accept long-term maintenance debt. If you want an actively maintained dependency, upstream is the safer default.

Prefer upstream unless you are locked to this fork's legacy patches. This fork looks like a stale, heavily diverged snapshot with meaningful local customization, but it is far behind current folly and likely missing many newer fixes and build/platform improvements.

Prefer this fork only if you specifically want its custom local changes and can accept a frozen, highly diverged Folly base. For most adopters, upstream is the better choice because this fork is stale and likely missing many newer fixes and features.

Prefer this fork only if you specifically need its older local patches and are willing to own the maintenance burden. For most adopters, upstream is the better choice because this fork is materially stale and diverged.

Fork comparison

jbandela/folly

38/100

stale

significant_divergence

Prefer upstream unless you specifically need this old snapshot’s local patches; this fork is too stale and divergent for most new adopters.

Likely purpose

A very old, lightly modified Folly snapshot for local use or experimentation, with a few portability and low-level correctness patches layered onto an upstream base.

Best for

Teams maintaining legacy code that already depends on this exact snapshot; Developers who want a frozen, minimal fork with a few local correctness patches; People studying historical Folly behavior rather than adopting a current library

Additional features

In-place `ProducerConsumerQueue` support
Atomic/memory-order correctness fixes in low-level containers
Safer allocation handling around `malloc`/`realloc`
Path portability cleanup for `fbstring`-related code
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

Hundreds of upstream commits of later Folly work, including modern C++20-era library evolution
Active maintenance and ongoing bugfixes from upstream
Modern build and packaging paths that exist upstream today, including newer CMake/Buck2-related integration
Broad compatibility and platform coverage improvements accumulated upstream over time
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream operational features such as auth, admin, or session handling may be reduced or absent.

Strengths

Very small, targeted local patches rather than a broad rewrite
May suit users who specifically need the queue and atomic/memory fixes represented in the fork
Could be easier to reason about than current upstream if you want a frozen legacy snapshot

Risks

Extremely stale: last pushed in 2012 and far behind upstream
Large divergence with massive deletion count suggests many upstream capabilities are absent or inaccessible
High maintenance burden if you need to integrate with modern toolchains or current Folly APIs
Low confidence for new adopters because the fork looks abandoned