Discofork
Repository brief

amruthpillai/reactive-resume

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:48:18.141Z
1mo ago

amruthpillai/reactive-resume

Reactive Resume is a popular, actively maintained open-source resume builder focused on privacy, self-hosting, and portability. It has strong adoption signals (36,035 stars, 3,969 forks) and recent commits as of 2026-03-29, including translation syncs, dependency updates, and MCP-related work. Forks are likely most interesting if you want to customize a mature TypeScript/Node.js app with built-in templates, AI integrations, localization, and self-hosted deployment support.

GitHub
Loading tags...
Stars36,035
Forks3,969
Default branchmain
Last pushed2026-03-29T22:21:28Z
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
Selected

Choose this fork if you want a resume listing product with featured/public discovery workflows and are comfortable giving up some upstream builder functionality and freshness. Avoid it if you need the mature upstream resume-builder experience, especially exports and ongoing upstream updates.

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.

amruthpillai/reactive-resume · Discofork