A · leads
reactive-resume
95.9
45,854 stars · MIT
Self-Hosted
reactive-resume leads by 4.7 · narrow
A · leads
95.9
45,854 stars · MIT
B
91.2
96,832 stars · license n/a
reactive-resume versus Stirling-PDF is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 95.9 for reactive-resume and 91.2 for Stirling-PDF.
Stirling-PDF has 96,832 GitHub stars to reactive-resume's 45,854, a gap of 50,978 (2.11×). Forks are 4,959 for reactive-resume and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 93 versus 100.
Push history: reactive-resume was last pushed on 16 November 2026 (1 day ago), and Stirling-PDF was last pushed on 17 November 2026 (0 days ago). Open issues stand at 7 for reactive-resume (0.000 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
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. Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for reactive-resume and 30 for Stirling-PDF. This is a procurement signal, not legal advice.
In Self-Hosted, both reactive-resume (45,854 stars) and Stirling-PDF (96,832 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, Stirling-PDF is unpriced in this catalog.
The lead is split. reactive-resume is furthest ahead on license flexibility (96 to 30), while Stirling-PDF is furthest ahead on fork community (100 to 93). Choose the dimension a rollout cannot compromise on.
reactive-resume finishes ahead at 95.9 against Stirling-PDF at 91.2, a 4.7 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 | Stirling-PDF |
|---|---|---|
| GitHub stars | 45,854 | 96,832 |
| Forks | 4,959 | 9,373 |
| Open issues | 7 | 448 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 93 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 95.9 | 91.2 |
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!
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Stirling-PDF has more GitHub stars: 96,832 versus 45,854 for reactive-resume. The gap is 50,978 stars.
Stirling-PDF 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 Stirling-PDF 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. Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
reactive-resume scores 95.9 and Stirling-PDF scores 91.2. This page calls that a narrow lead for reactive-resume.