Comparison
browser-use vs skyvern
Verdict
Unverified catalog guidance: browser-use: browser-use is a Python-based repository for AI agents designed for browser automation using Playwright. skyvern: Skyvern automates browser-based workflows with Python, using libraries such as Playwright and Selenium.
Markdown twin · browser-use alternatives · skyvern alternatives
GraphCanon updated Oct 23, 2026
Trust & integrity
| Signal | browser-use | skyvern |
|---|---|---|
| Maintenance | Very active (2d since push) As of Sep 18, 2026 · github_public_v1 | Very active (0d since push) As of Oct 23, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 18, 2026 · github_public_v1 | Not a fork · Organization account As of Oct 23, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Sep 18, 2026 · osv@v1 | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
| MCP manifest observations | Published findings As of Sep 18, 2026 · mcp_manifest@v1 | Published findings As of Jul 15, 2026 · mcp_manifest@v1 |
Tagline
- browser-use
- Agents that use the browser
- skyvern
- Automate browser based workflows with AI
Stars
- browser-use
- 115k
- skyvern
- 23k
Forks
- browser-use
- 13k
- skyvern
- 2.2k
Open issues
- browser-use
- 439
- skyvern
- 290
Language
- browser-use
- Python
- skyvern
- Python
Adopt for
- browser-use
- Unverified catalog guidance: browser-use is a Python-based repository for AI agents designed for browser automation using Playwright.
- skyvern
- Unverified catalog guidance: Skyvern automates browser-based workflows with Python, using libraries such as Playwright and Selenium.
Persona
- browser-use
- -
- skyvern
- -
Runtime
- browser-use
- -
- skyvern
- -
License
- browser-use
- MIT
- skyvern
- AGPL-3.0
Last pushed
- browser-use
- Sep 15, 2026
- skyvern
- Oct 23, 2026
Categories
- browser-use
- AI Agents, Developer Tools
- skyvern
- AI Agents, Developer Tools
Trust and health
Days since push
- browser-use
- 2d
- skyvern
- 0d
Open issues (recorded)
- browser-use
- 439
- skyvern
- 290
Stars delta
- browser-use
- +5.7k (30d)
- skyvern
- +259 (30d)
Open issues delta
- browser-use
- +82 (30d)
- skyvern
- +52 (30d)
Full report
- browser-use
- Trust report
- skyvern
- Trust report
Choose browser-use if…
- License: browser-use is MIT, skyvern is AGPL-3.0.
- Tags unique to browser-use: ai-agents, ai-tools, playwright, python.
- Unverified catalog guidance: When you need to automate browser actions with AI agents and prefer using Playwright for its robust capabilities in handling modern web applications.
When NOT to use browser-use
- Unverified catalog guidance: If your project requires a different browser automation tool that is not Playwright, as browser-use is specifically tailored for Playwright integration.
- Unverified catalog guidance: When detailed documentation and integrations provided by browser-use do not align with your project's specific needs or if you prefer a more generalized approach to browser automation.
Choose skyvern if…
- License: skyvern is AGPL-3.0, browser-use is MIT.
- Tags unique to skyvern: ai, api, automation, powerautomate.
- Unverified catalog guidance: When you require an AI-driven approach to automate browser tasks through a user interface or a Python SDK.
When NOT to use skyvern
- Unverified catalog guidance: When your project strictly requires proprietary or closed-source software incompatible with AGPL-3.0 licensing conditions.
- Unverified catalog guidance: For deployments where manual configuration of each dependency and integration is not feasible or desirable due to complexity.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (browser-use/browser-use) · observed Sep 20, 2026
- GitHub forks (browser-use/browser-use) · observed Sep 20, 2026
- Last push (browser-use/browser-use) · observed Sep 15, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Sep 18, 2026
- Trust scan (lockfile / OSV) · observed Sep 18, 2026
- GitHub stars (Skyvern-AI/skyvern) · observed Oct 23, 2026
- GitHub forks (Skyvern-AI/skyvern) · observed Oct 23, 2026
- Last push (Skyvern-AI/skyvern) · observed Oct 23, 2026
- License file (AGPL-3.0) · observed Oct 23, 2026
- Decision facts (enrichment) · observed Jul 16, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: browser-use 115k · skyvern 23k (synced Sep 20, 2026).
Common questions
- What is the difference between browser-use and skyvern?
- browser-use: Agents that use the browser. skyvern: Automate browser based workflows with AI. See the comparison table for recorded GitHub metadata and shared categories.
- When should I choose browser-use over skyvern?
- For browser-use, compare these recorded points with skyvern: License: browser-use is MIT, skyvern is AGPL-3.0; Tags unique to browser-use: ai-agents, ai-tools, playwright, python; Unverified catalog guidance: When you need to automate browser actions with AI agents and prefer using Playwright for its robust capabilities in handling modern web applications.
- When should I choose skyvern over browser-use?
- For skyvern, compare these recorded points with browser-use: License: skyvern is AGPL-3.0, browser-use is MIT; Tags unique to skyvern: ai, api, automation, powerautomate; Unverified catalog guidance: When you require an AI-driven approach to automate browser tasks through a user interface or a Python SDK.
- When should I avoid browser-use?
- Unverified catalog guidance: If your project requires a different browser automation tool that is not Playwright, as browser-use is specifically tailored for Playwright integration. Unverified catalog guidance: When detailed documentation and integrations provided by browser-use do not align with your project's specific needs or if you prefer a more generalized approach to browser automation.
- When should I avoid skyvern?
- Unverified catalog guidance: When your project strictly requires proprietary or closed-source software incompatible with AGPL-3.0 licensing conditions. Unverified catalog guidance: For deployments where manual configuration of each dependency and integration is not feasible or desirable due to complexity.
- Is browser-use or skyvern more popular on GitHub?
- browser-use has more recorded GitHub stars (115,057 vs 23,253). Stars measure visibility, not whether either tool fits your constraints.
- Which licenses are recorded for browser-use and skyvern?
- browser-use: MIT. skyvern: AGPL-3.0. Check each repository's current license and terms before use. Public GitHub hosting alone does not establish open-source licensing.
- Where can I find alternatives to browser-use or skyvern?
- GraphCanon lists candidates at browser-use alternatives and skyvern alternatives (browser-use markdown twin, skyvern markdown twin). The discovery order uses stored relationship proposals and shared categories; it is not a verified replacement ranking.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, browser-use or skyvern?
- browser-use: Very active. skyvern: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for browser-use and skyvern?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: browser-use trust report; skyvern trust report.