A · level
pentagi
98.2
34,396 stars · MIT
Self-Hosted
Too close to call · 98.2 to 99.0
A · level
98.2
34,396 stars · MIT
B · level
99.0
45,854 stars · MIT
pentagi 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. pentagi is written mainly in Go; reactive-resume is written mainly in TypeScript. The composite score is 98.2 for pentagi and 99.0 for reactive-resume.
reactive-resume has 45,854 GitHub stars to pentagi's 34,396, a gap of 11,458 (1.33×). Forks are 5,447 for pentagi and 4,959 for reactive-resume. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 100 versus 99.
Push history: pentagi was last pushed on 13 November 2026 (3 days ago), and reactive-resume was last pushed on 16 November 2026 (1 day ago). Open issues stand at 76 for pentagi (0.002 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 pentagi 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 pentagi (34,396 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: pentagi is open source, reactive-resume is open source.
The lead is split. pentagi is furthest ahead on fork community (100 to 99), while reactive-resume is furthest ahead on adoption (100 to 97). Choose the dimension a rollout cannot compromise on.
Composite score: pentagi 98.2, reactive-resume 99.0. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | pentagi | reactive-resume |
|---|---|---|
| GitHub stars | 34,396 | 45,854 |
| Forks | 5,447 | 4,959 |
| Open issues | 76 | 7 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 99 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.2 | 99.0 |
Fully autonomous AI Agents system capable of performing complex penetration testing tasks
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 34,396 for pentagi. The gap is 11,458 stars.
reactive-resume was pushed more recently: 16 November 2026 versus 13 November 2026 for pentagi. That is 2 days apart.
Yes. This catalog marks both pentagi and reactive-resume as self-hostable. Confirm each project's deploy docs before you plan a migration.
pentagi 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.
Neither tool clears a one-point margin. pentagi scores 98.2 and reactive-resume scores 99.0.