amruthpillai/reactive-resume

Choose this fork only if OIDC login, HTTPS cookie hardening, or custom font/branding changes are central to your use case. If you want the broadest upstream feature set and easiest maintenance path, upstream is the safer choice.

Choose this fork only if you want its custom typography/artboard direction and are comfortable carrying a large upstream delta. If you want the most current, lowest-risk Reactive Resume base, upstream is the safer choice.

Prefer this fork only if you need its Android-specific and custom workflow changes. For most adopters, upstream is the better base because it is far more current and actively maintained.

Choose this fork if you want the upstream project as a starting point for a substantially different enterprise workflow. Choose upstream instead if you want the latest resume-builder features, translations, and lower-maintenance adoption.

Choose this fork only if its typography/localization-heavy changes match your needs and you are prepared to maintain a large divergence from upstream. If you want the newest Reactive Resume fixes, this fork is a poor default because it is stale and significantly behind current upstream activity.

Choose this fork only if its specific 4.x-era tweaks solve your problem and you are comfortable owning the maintenance gap. For most adopters, upstream Reactive Resume is the safer default because this fork is materially stale and has clearly dropped or lagged core functionality.

Choose this fork only if the Android/mobile direction or its custom account/localization changes are specifically what you need. If you want a current, low-maintenance resume builder, upstream is the better choice because this fork is stale and materially behind.

Prefer this fork only if you need its custom artboard/font/import behavior and are willing to own a long-stale, highly divergent codebase. If you mainly want the current Reactive Resume product, upstream is the safer choice.