openyak

One chat. Every agent. A universal interface for AI agents running on your computer.

Browser & Computer Use TypeScript Grade C Listed Apache-2.0
58.5/100
Rank #658 of 1328
Compare openyak

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-05 · 15d ago
Recent change
No recent signal change

Is openyak safe? openyak scores 58.5/100 (Grade C), ranked #658 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.2/10; 59% of recent commits are signed; last pushed 2026-09-05. 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
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-11
Rank Moved
Rank dropped 20 spots (#614 → #634)
2026-09-08
Rank Moved
Rank dropped 12 spots (#595 → #607)
2026-09-07
Scorecard Added
OSSF Scorecard: 6.2/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
67.7
Activity sub-score · out of 100
#19

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

Signals refreshed 2026-09-20 21:32 UTC · Repo last pushed 15 days ago

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
708
Forks
61
Last Push
2026-09-05
15 days ago
Commits (4 wk)
35
Downloads (7d)
HN mentions (30d)
Open Issues
9
Rank Change
▼5
was #653

Analysis

HVTrust Dimensions vs Browser & Computer Use

58.5 / 100 · 100.0% confidence

openyak Browser & Computer Use average (42 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.7 / 25
1.1 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.5 below avg 12.3
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
1.9 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
17.2 / 20
4.0 above avg 13.2
AdoptionLog-scaled stars · package downloads
6.8 / 20
4.5 below avg 11.3

Activity Inputs

67.7 / 100
StarsRepository reach
17.1 / 30
FreshnessLast push recency
22.9 / 25
ActivityRecent commits
19.4 / 25
CommunityFork signal
8.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.2 / 10
OpenSSF Scorecard · scanned Sep 12, 2026
Signed Commits
59%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 10
SAST 0
Security-Policy 10
Signed-Releases 8
Token-Permissions 10
Vulnerabilities 10

Is openyak safe?

openyak has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does openyak publish package provenance?
No published build provenance is currently detected for openyak. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does openyak have an OpenSSF Scorecard?
openyak has an OpenSSF Scorecard score of 6.2/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 openyak actively maintained?
Maintained. Last push was 15 days ago.
What license does openyak use?
openyak ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are openyak's commits signed?
59% of the last 100 commits to openyak 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.

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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
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 openyak'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-09-05
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI
2026-09-05
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, Google Gemini, Multi-provider (LiteLLM), OpenAI
2026-09-03
Mcp Status Changed
Detected MCP server support changed: declared → none

Maintain openyak?

For maintainers

HVTrust scores openyak 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 18MCP 2Listed 1Surface 1Surface 1Surface 1HVTrust 1Grade 1Scorecard 1
2026-09-11
Rank Moved
Rank dropped 20 spots (#614 → #634)
2026-09-08
Rank Moved
Rank dropped 12 spots (#595 → #607)
2026-09-07
Scorecard Added
OSSF Scorecard: 6.2/10
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 705 spots (#1300 → #595)
2026-09-07
HVTrust Changed
HVTrust up 36.6pts (22.8 → 59.4)
2026-09-05
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI
2026-09-05
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-05
Rank Moved
Rank dropped 21 spots (#1272 → #1293)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, Google Gemini, Multi-provider (LiteLLM), OpenAI
2026-09-03
Mcp Status Changed
Detected MCP server support changed: declared → none
2026-09-02
Rank Moved
Rank dropped 25 spots (#1236 → #1261)
2026-09-01
Rank Moved
Rank dropped 20 spots (#1216 → #1236)
2026-08-31
Rank Moved
Rank dropped 24 spots (#1192 → #1216)
2026-08-30
Rank Moved
Rank dropped 27 spots (#1165 → #1192)
2026-08-29
Rank Moved
Rank dropped 27 spots (#1138 → #1165)
2026-08-28
Rank Moved
Rank dropped 21 spots (#1117 → #1138)
2026-08-26
Rank Moved
Rank dropped 68 spots (#1054 → #1122)
2026-08-23
Rank Moved
Rank dropped 12 spots (#1036 → #1048)
2026-08-19
Rank Moved
Rank dropped 29 spots (#1011 → #1040)
2026-08-16
Rank Moved
Rank dropped 21 spots (#996 → #1017)
2026-08-13
Rank Moved
Rank dropped 10 spots (#989 → #999)
2026-08-12
Rank Moved
Rank rose 12 spots (#1001 → #989)
2026-08-10
Rank Moved
Rank dropped 58 spots (#940 → #998)
2026-08-08
Rank Moved
Rank dropped 449 spots (#482 → #931)
2026-08-06
Newly Listed
First tracked at rank #492

Embed Badge Badge guide for maintainers →

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

Other agents in Browser & Computer Use

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