A
navidrome
90.5
24,808 stars · GPL-3.0
Self-Hosted
reactive-resume leads by 8.6 · clear
A
90.5
24,808 stars · GPL-3.0
B · leads
99.1
45,854 stars · MIT
navidrome 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. navidrome is written mainly in Go; reactive-resume is written mainly in TypeScript. The composite score is 90.5 for navidrome and 99.1 for reactive-resume.
reactive-resume has 45,854 GitHub stars to navidrome's 24,808, a gap of 21,046 (1.85×). Forks are 1,822 for navidrome and 4,959 for reactive-resume. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 88 versus 100.
Push history: navidrome 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 318 for navidrome (0.013 per star) and 7 for reactive-resume (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
navidrome is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. License scores in this pair are 64 for navidrome and 96 for reactive-resume. This is a procurement signal, not legal advice.
In Self-Hosted, both navidrome (24,808 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: navidrome is open source, reactive-resume is open source.
reactive-resume is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
reactive-resume finishes ahead at 99.1 against navidrome at 90.5, a 8.6 point clear 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 | navidrome | reactive-resume |
|---|---|---|
| GitHub stars | 24,808 | 45,854 |
| Forks | 1,822 | 4,959 |
| Open issues | 318 | 7 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 84 | 96 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.5 | 99.1 |
🎧 Your Personal Streaming Service
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!
reactive-resume has more GitHub stars: 45,854 versus 24,808 for navidrome. The gap is 21,046 stars.
navidrome was pushed more recently: 17 November 2026 versus 16 November 2026 for reactive-resume. That is 1 days apart.
Yes. This catalog marks both navidrome and reactive-resume as self-hostable. Confirm each project's deploy docs before you plan a migration.
navidrome is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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.
reactive-resume scores 99.1 and navidrome scores 90.5. This page calls that a clear lead for reactive-resume.