A · leads
pentagi
98.8
34,396 stars · MIT
Self-Hosted
pentagi leads by 3.1 · narrow
A · leads
98.8
34,396 stars · MIT
B
95.7
37,875 stars · Apache-2.0
pentagi versus QwenPaw 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; QwenPaw is written mainly in TypeScript. The composite score is 98.8 for pentagi and 95.7 for QwenPaw.
QwenPaw has 37,875 GitHub stars to pentagi's 34,396, a gap of 3,479 (1.10×). Forks are 5,447 for pentagi and 3,293 for QwenPaw. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 94.
Push history: pentagi was last pushed on 13 November 2026 (3 days ago), and QwenPaw was last pushed on 17 November 2026 (0 days ago). Open issues stand at 76 for pentagi (0.002 per star) and 1,167 for QwenPaw (0.031 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
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. QwenPaw is listed as Apache-2.0, 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 96 for pentagi and 96 for QwenPaw. This is a procurement signal, not legal advice.
In Self-Hosted, both pentagi (34,396 stars) and QwenPaw (37,875 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, QwenPaw is open source.
The lead is split. pentagi is furthest ahead on issue health (96 to 70), while QwenPaw is furthest ahead on adoption (100 to 99). Choose the dimension a rollout cannot compromise on.
pentagi finishes ahead at 98.8 against QwenPaw at 95.7, a 3.1 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 | pentagi | QwenPaw |
|---|---|---|
| GitHub stars | 34,396 | 37,875 |
| Forks | 5,447 | 3,293 |
| Open issues | 76 | 1,167 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.8 | 95.7 |
Fully autonomous AI Agents system capable of performing complex penetration testing tasks
Your Personal AI Assistant; easy to install, deploy on your own machine or on the cloud; supports multiple chat apps with easily extensible capabilities.
QwenPaw has more GitHub stars: 37,875 versus 34,396 for pentagi. The gap is 3,479 stars.
QwenPaw was pushed more recently: 17 November 2026 versus 13 November 2026 for pentagi. That is 3 days apart.
Yes. This catalog marks both pentagi and QwenPaw 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. QwenPaw is listed as Apache-2.0, 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.
pentagi scores 98.8 and QwenPaw scores 95.7. This page calls that a narrow lead for pentagi.