A
reactive-resume
96.1
45,854 stars · MIT
Self-Hosted
uptime-kuma leads by 1.8 · narrow
A
96.1
45,854 stars · MIT
B · leads
97.9
94,538 stars · MIT
reactive-resume versus uptime-kuma is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. reactive-resume is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 96.1 for reactive-resume and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to reactive-resume's 45,854, a gap of 48,684 (2.06×). Forks are 4,959 for reactive-resume and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 94 versus 100.
Push history: reactive-resume was last pushed on 16 November 2026 (1 day ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 7 for reactive-resume (0.000 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both reactive-resume and uptime-kuma are listed as MIT. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both reactive-resume (45,854 stars) and uptime-kuma (94,538 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: reactive-resume is open source, uptime-kuma is open source.
The lead is split. reactive-resume is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on fork community (100 to 94). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against reactive-resume at 96.1, a 1.8 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | reactive-resume | uptime-kuma |
|---|---|---|
| GitHub stars | 45,854 | 94,538 |
| Forks | 4,959 | 8,860 |
| Open issues | 7 | 852 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.1 | 97.9 |
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 45,854 for reactive-resume. The gap is 48,684 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 16 November 2026 for reactive-resume. That is 1 days apart.
Yes. This catalog marks both reactive-resume and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
reactive-resume is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. uptime-kuma is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uptime-kuma scores 97.9 and reactive-resume scores 96.1. This page calls that a narrow lead for uptime-kuma.