Is Skyvern safe?
Skyvern scores 79.4/100 (Grade B), ranked #43 of 328 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.0/10;
recent commits are unsigned;
last pushed 2026-07-11. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
79.4/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
16.2/25
What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-06-20
Rank Moved
Rank dropped 12 spots (#21 → #33)
2026-06-20
HVTrust Changed
HVTrust down 4.7pts (88.2 → 83.5)
Maintainer Checklist
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 refreshed2026-07-11 05:00 UTC·Repo last pushed today
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
22.2k
Forks
2.1k
Last Push
2026-07-11
today
Commits (4 wk)
630
Downloads (7d)
1,326
pypi
HN mentions (30d)
2
Open Issues
36
Rank Change
=
was #43
Analysis
HVTrust Dimensions
79.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
16.2 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
14.4 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
14.6 / 20
Activity Inputs
91.5 / 100
StarsRepository reach
26.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.4 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
7.0 / 10
OpenSSF Scorecard · scanned Jul 8, 2026
Signed Commits
—
Unable to query
Binary-Artifacts10
Branch-Protection8
CI-Tests10
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing10
License10
Maintained10
Packaging10
Pinned-Dependencies4
SAST10
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
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.0/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.
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.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
browser
code
database
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.
Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Azure OpenAI, Google Gemini, OpenAI, Postgres, Redis
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-05-31
Provenance Added
Package provenance attestation detected
Maintain Skyvern?
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.
