Is openyak safe to use?

openyak has an HVTrust score of 21.3/100 (Grade D), ranked #1001 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for openyak?

openyak scores 21.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 704 GitHub stars and is categorized under Browser & Computer Use.

openyak

openyak/openyak

Open-source local-first AI agent for desktop work. No account, no telemetry: use local models with Ollama/Rapid-MLX or b

Browser & Computer Use Python Grade D Listed Apache-2.0

21.3/100

Rank #1001 of 1283

Compare openyak

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-09 · 2d ago

Recent change

Rank +2

Is openyak safe? openyak scores 21.3/100 (Grade D), ranked #1001 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 54% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#37 Obscura — 27.0 (D) → #38 arbigent — 24.3 (D) → #39 openocta — 21.7 (D) → #41 TuriX — 20.6 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

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

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for openyak View Browser & Computer Use Report missing data

69.3

Activity sub-score · out of 100

#40

In Browser & Computer Use

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

Activity & Reach

Stars

704

Forks

Last Push

2026-08-09

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #998

Analysis

HVTrust Dimensions vs Browser & Computer Use

21.3 / 100 · 50.0% confidence

openyak Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

2.7 / 25

4.7 below avg 7.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.6 below avg 12.4

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

2.3 below avg 10.8

Maintenance60% last-push freshness · 40% commit activity

18.0 / 20

4.9 above avg 13.1

AdoptionLog-scaled stars · package downloads

6.8 / 20

4.4 below avg 11.2

Activity Inputs

69.3 / 100

StarsRepository reach

17.1 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

19.3 / 25

CommunityFork signal

8.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

54%

of last 100 commits verified

Is openyak safe?

Public trust evidence for openyak is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

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?

No OpenSSF Scorecard data is currently published for openyak. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is openyak actively maintained?

Actively maintained. The repository was pushed to within the last 2 day(s).

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?

54% 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

4 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface 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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

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

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON