A · leads
memos
99.1
64,520 stars · MIT
Self-Hosted
memos leads by 1.0 · narrow
A · leads
99.1
64,520 stars · MIT
B
98.1
45,854 stars · MIT
memos versus reactive-resume is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. memos is written mainly in Go; reactive-resume is written mainly in TypeScript. The composite score is 99.1 for memos and 98.1 for reactive-resume.
memos has 64,520 GitHub stars to reactive-resume's 45,854, a gap of 18,666 (1.41×). Forks are 4,972 for memos and 4,959 for reactive-resume. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 100.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and reactive-resume was last pushed on 16 November 2026 (1 day ago). Open issues stand at 63 for memos (0.001 per star) and 7 for reactive-resume (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
Both memos and reactive-resume 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 memos (64,520 stars) and reactive-resume (45,854 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: memos is open source, reactive-resume is open source.
memos is ahead on every scored dimension that is not level. Level dimensions: recent activity, fork community, issue health, license flexibility, self-hosting. The widest gap is adoption at 3 points (100 vs 97), and the tightest is self-hosting at 0 points (100 vs 100).
memos finishes ahead at 99.1 against reactive-resume at 98.1, a 1.0 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 | memos | reactive-resume |
|---|---|---|
| GitHub stars | 64,520 | 45,854 |
| Forks | 4,972 | 4,959 |
| Open issues | 63 | 7 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 98.1 |
Memos is an open-source, self-hosted note-taking app that brings your everyday thoughts together in a personal timeline. Your data stays yours, and you choose what to keep private or share.
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!
memos has more GitHub stars: 64,520 versus 45,854 for reactive-resume. The gap is 18,666 stars.
memos was pushed more recently: 17 November 2026 versus 16 November 2026 for reactive-resume. That is 1 days apart.
Yes. This catalog marks both memos and reactive-resume as self-hostable. Confirm each project's deploy docs before you plan a migration.
memos 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
memos scores 99.1 and reactive-resume scores 98.1. This page calls that a narrow lead for memos.