A · leads
MoneyPrinterTurbo
99.1
144,149 stars · MIT
Workflow Automation
MoneyPrinterTurbo leads by 2.4 · narrow
A · leads
99.1
144,149 stars · MIT
B
96.7
95,849 stars · Apache-2.0
MoneyPrinterTurbo versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. MoneyPrinterTurbo is written mainly in Python; puppeteer is written mainly in TypeScript. The composite score is 99.1 for MoneyPrinterTurbo and 96.7 for puppeteer.
MoneyPrinterTurbo has 144,149 GitHub stars to puppeteer's 95,849, a gap of 48,300 (1.50×). Forks are 23,122 for MoneyPrinterTurbo and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 91.
Push history: MoneyPrinterTurbo was last pushed on 17 November 2026 (0 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 86 for MoneyPrinterTurbo (0.001 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
MoneyPrinterTurbo 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. puppeteer 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 MoneyPrinterTurbo and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both MoneyPrinterTurbo (144,149 stars) and puppeteer (95,849 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: MoneyPrinterTurbo is open source, puppeteer is open source.
MoneyPrinterTurbo is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 9 points (100 vs 91), and the tightest is self-hosting at 0 points (100 vs 100).
MoneyPrinterTurbo finishes ahead at 99.1 against puppeteer at 96.7, a 2.4 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 | MoneyPrinterTurbo | puppeteer |
|---|---|---|
| GitHub stars | 144,149 | 95,849 |
| Forks | 23,122 | 9,607 |
| Open issues | 86 | 201 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 91 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 96.7 |
利用 AI 大模型和自动化工作流,根据主题或关键词一键生成高清短视频。Generate HD short videos from a topic or keyword with an automated AI workflow.
JavaScript API for Chrome and Firefox
MoneyPrinterTurbo has more GitHub stars: 144,149 versus 95,849 for puppeteer. The gap is 48,300 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both MoneyPrinterTurbo and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
MoneyPrinterTurbo 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. puppeteer 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.
MoneyPrinterTurbo scores 99.1 and puppeteer scores 96.7. This page calls that a narrow lead for MoneyPrinterTurbo.