Skyvern

Automate browser based workflows with AI

Browser & Computer Use Python Grade A Listed AGPL-3.0
82.5/100
Rank #62 of 1308
Compare Skyvern

How does it stack up against its Browser & Computer Use neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade A · 4/5 signals
Last push
2026-08-25 · 0d ago
Recent change
No recent signal change

Is Skyvern safe? Skyvern scores 82.5/100 (Grade A), ranked #62 of 1308 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.4/10; recent commits are unsigned; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Maintainer Checklist
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
91.7
Activity sub-score · out of 100
#5

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-25 08:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
22.8k
Forks
2.1k
Last Push
2026-08-25
today
Commits (4 wk)
419
Downloads (7d)
1,326
pypi
HN mentions (30d)
2
Open Issues
35
Rank Change
=
was #62

Analysis

HVTrust Dimensions vs Browser & Computer Use

82.5 / 100 · 100.0% confidence

Skyvern Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.8 / 25
9.3 above avg 7.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.6 above avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
14.8 / 17
4.0 above avg 10.8
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.2 above avg 12.8
AdoptionLog-scaled stars · package downloads
14.6 / 20
3.3 above avg 11.3

Activity Inputs

91.7 / 100
StarsRepository reach
26.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.5 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
7.4 / 10
OpenSSF Scorecard · scanned Aug 24, 2026
Signed Commits
Unable to query
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 0
Code-Review 1
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 10
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 4
SAST 10
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 5

Is Skyvern safe?

Public supply-chain signals for Skyvern are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Skyvern carries less obvious unverified-evidence risk than projects with thin signals.
Does Skyvern publish package provenance?
Yes. Skyvern's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Skyvern have an OpenSSF Scorecard?
Skyvern has an OpenSSF Scorecard score of 7.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Skyvern actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Skyvern use?
Skyvern ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Skyvern head-to-head

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Skyvern appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Skyvern's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-05-31
Provenance Added
Package provenance attestation detected

Maintain Skyvern?

For maintainers

HVTrust scores Skyvern from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
HVTrust 2Grade 2Score 1Provenance 1Rank 1
2026-07-23
Grade Changed
Trust grade A → B
2026-07-21
Grade Changed
Trust grade B → A
2026-06-20
Rank Moved
Rank dropped 12 spots (#21 → #33)
2026-06-20
HVTrust Changed
HVTrust down 4.7pts (88.2 → 83.5)
2026-05-31
Provenance Added
Package provenance attestation detected
2026-05-29
HVTrust Changed
HVTrust up 10.0pts (62.9 → 72.9)
2026-05-28
Activity Score Changed
Activity score up 25pts (66 → 91)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 82.5 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/skyvern.svg)](https://hvtracker.net/agents/skyvern)
HTML:
<a href="https://hvtracker.net/agents/skyvern"><img src="https://hvtracker.net/badge/skyvern.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON