Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for ops, RPA, and back-office automation teams that need to automate workflows on legacy web apps (no APIs, no selectors, just a browser) where traditional RPA (UiPath, Automation Anywhere) is too brittle and too expensive.
Where this stands now
Skyvern-AI/skyvern ranks #327 of 2355 tracked Radar items by composite score (8.3 against a section median of 5.2). The section currently carries 1248 Bronze, 645 Gold, 462 Silver. RepoRadar has retained observations for this record since 2026-06-17 (103 days in the current window). Signal extremes versus the section: momentum at the 90th percentile.
Who should use it
Who should skip it
Skip Skyvern-AI/skyvern if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
Skyvern-AI/skyvern is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-17; the source record was last checked on 2026-06-17. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, Skyvern-AI/skyvern is strongest on workflow potential (9.4) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The Skyvern-AI/skyvern record combines a 8.3/10 composite score with separate popularity (88.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
AGPL-3.0 license: any modifications to a self-hosted instance that are exposed over a network must be open-sourced — acceptable for internal use, restrictive if you plan to resell as a SaaS; Headless browser automation consumes significant compute and depends on LLM API costs per run — benchmark on real workflows before scaling; Captcha / MFA flows require human-in-the-loop — factor in human review time for high-volume automation.