Skyvern

Automate browser based workflows with AI

Browser & Computer Use Python Listed AGPL-3.0

Is Skyvern safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.4 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Skyvern
Suggest a correction

In detail: Skyvern scores 87.0/100 (Grade A), ranked #60 of 1371 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; 100% of recent commits are signed; no published advisory affects its latest release (skyvern); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Skyvern could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Skyvern and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/Skyvern-AI/skyvern, AGPL-3.0, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.4/10 (scanned Sep 26, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection8
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    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
  3. Published packages Partly attested

    • PyPI skyvern Source link isn't a GitHub repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: skyvern 1.0.55. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Skyvern.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues Skyvern’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Skyvern compares in Browser & Computer Use

  1. #5 Stagehand 88.9 +1.9
  2. #6 Agent Browser 87.7 +0.7
  3. #7 Skyvern 87.0 this agent
  4. #8 Camofox Browser 81.7 −5.3
  5. #9 agent-device 78.6 −8.4

Bars show each HVTrust score; the tick marks Skyvern’s 87.0.

Where the 87.0 comes from

HVTrust dimensions vs the Browser & Computer Use average

87.0 / 100 · 100.0% confidence

Skyvern Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
21.7 / 25
12.4 above avg 9.3
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
3.4 above avg 11.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
14.7 / 20
4.0 above avg 10.7

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 22 spots (#42 → #64)
2026-09-21
Rank Moved
Rank rose 14 spots (#57 → #43)
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
91.7
Activity sub-score · out of 100
#7

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-10-09 08:15 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
23.2k
Forks
2.2k
Last Push
2026-10-09
today
Commits (4 wk)
291
Downloads (7d)
1,410
pypi
HN mentions (30d)
4
Open Issues
47
Rank Change
▼1
was #59

Analysis

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

Common questions about Skyvern

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.
Are Skyvern's commits signed?
100% of the last 100 commits to Skyvern are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

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
Rank 4Grade 2HVTrust 1
2026-09-23
Rank Moved
Rank dropped 22 spots (#42 → #64)
2026-09-21
Rank Moved
Rank rose 14 spots (#57 → #43)
2026-09-03
Rank Moved
Rank rose 33 spots (#72 → #39)
2026-09-03
HVTrust Changed
HVTrust up 4.4pts (82.5 → 86.9)
2026-08-31
Rank Moved
Rank dropped 12 spots (#67 → #79)
2026-07-23
Grade Changed
Trust grade A → B
2026-07-21
Grade Changed
Trust grade B → A

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 87.0 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.4 · Raw JSON