A · leads
gpt-researcher
97.3
30,757 stars · Apache-2.0
Workflow Automation
gpt-researcher leads by 2.9 · narrow
A · leads
97.3
30,757 stars · Apache-2.0
B
94.4
27,230 stars · MIT
gpt-researcher versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. gpt-researcher is written mainly in Python; vagrant is written mainly in Ruby. The composite score is 97.3 for gpt-researcher and 94.4 for vagrant.
gpt-researcher has 30,757 GitHub stars to vagrant's 27,230, a gap of 3,527 (1.13×). Forks are 4,236 for gpt-researcher and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 99 versus 100.
Push history: gpt-researcher was last pushed on 12 November 2026 (4 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 56 for gpt-researcher (0.002 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 96 and 70; activity scores are 92 and 92.
gpt-researcher 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. vagrant 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 96 for gpt-researcher and 96 for vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both gpt-researcher (30,757 stars) and vagrant (27,230 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: gpt-researcher is open source, vagrant is open source.
The lead is split. gpt-researcher is furthest ahead on issue health (96 to 70), while vagrant is furthest ahead on fork community (100 to 99). Choose the dimension a rollout cannot compromise on.
gpt-researcher finishes ahead at 97.3 against vagrant at 94.4, a 2.9 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 | gpt-researcher | vagrant |
|---|---|---|
| GitHub stars | 30,757 | 27,230 |
| Forks | 4,236 | 4,491 |
| Open issues | 56 | 760 |
| Adoption | 100 | 99 |
| Activity | 92 | 92 |
| Community | 99 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.3 | 94.4 |
An autonomous agent that conducts deep research on any data using any LLM providers
Vagrant is a tool for building and distributing development environments.
gpt-researcher has more GitHub stars: 30,757 versus 27,230 for vagrant. The gap is 3,527 stars.
gpt-researcher was pushed more recently: 12 November 2026 versus 12 November 2026 for vagrant. That is 1 days apart.
Yes. This catalog marks both gpt-researcher and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
gpt-researcher 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. vagrant 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.
gpt-researcher scores 97.3 and vagrant scores 94.4. This page calls that a narrow lead for gpt-researcher.