Is openocta safe to use?

openocta has an HVTrust score of 51.2/100 (Grade C), ranked #893 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for openocta?

openocta scores 51.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.2k GitHub stars and is categorized under Browser & Computer Use.

openocta

openocta/openocta

OpenOcta is an open-source AIOps Agent installed on Windows & macOS.

Browser & Computer Use TypeScript Grade C Listed GPL-3.0

51.2/100

Rank #893 of 1328

Compare openocta

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 C · 2/5 signals

Last push

2026-09-16 · 4d ago

Recent change

License +1

Is openocta safe? openocta scores 51.2/100 (Grade C), ranked #893 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 2.9/10; 40% of recent commits are signed; last pushed 2026-09-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#25 Magentic-UI — 53.1 (C) → #26 autoMate — 52.7 (C) → #28 Agent-S — 50.8 (C) → #29 bb-browser — 49.4 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-16

License Changed

License changed from Apache-2.0 to GPL-3.0

2026-09-16

Rank Moved

Rank rose 16 spots (#902 → #886)

2026-09-11

Rank Moved

Rank dropped 16 spots (#872 → #888)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.9/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

72.2

Activity sub-score · out of 100

#27

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 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 →

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars

3.2k

Forks

397

Last Push

2026-09-16

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #894

Analysis

HVTrust Dimensions vs Browser & Computer Use

51.2 / 100 · 100.0% confidence

openocta Browser & Computer Use average (42 agents)

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

5.6 / 25

4.0 below 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

11.0 / 17

0.9 below avg 11.9

Maintenance60% last-push freshness · 40% commit activity

16.4 / 20

3.2 above avg 13.2

AdoptionLog-scaled stars · package downloads

8.4 / 20

2.9 below avg 11.3

Activity Inputs

72.2 / 100

StarsRepository reach

21.0 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

14.7 / 25

CommunityFork signal

12.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

2.9 / 10

OpenSSF Scorecard · scanned Sep 20, 2026

Signed Commits

40%

of last 100 commits verified

Binary-Artifacts 8

Branch-Protection 3

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 0

Is openocta safe?

Public trust evidence for openocta 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 openocta publish package provenance?

No published build provenance is currently detected for openocta. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does openocta have an OpenSSF Scorecard?

openocta has an OpenSSF Scorecard score of 2.9/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 openocta actively maintained?

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

What license does openocta use?

openocta ships under GPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are openocta's commits signed?

40% of the last 100 commits to openocta 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

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 openocta?

For maintainers

HVTrust scores openocta 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-09-16

License Changed

License changed from Apache-2.0 to GPL-3.0

2026-09-16

Rank Moved

Rank rose 16 spots (#902 → #886)

2026-09-11

Rank Moved

Rank dropped 16 spots (#872 → #888)

2026-09-08

Rank Moved

Rank dropped 10 spots (#860 → #870)

2026-09-07

Rank Moved

Rank dropped 38 spots (#822 → #860)

2026-09-06

Rank Moved

Rank dropped 13 spots (#809 → #822)

2026-09-05

Rank Moved

Rank dropped 60 spots (#749 → #809)

2026-09-04

Rank Moved

Rank dropped 32 spots (#717 → #749)

2026-09-03

Rank Moved

Rank dropped 35 spots (#682 → #717)

2026-09-02

Scorecard Added

OSSF Scorecard: 3.1/10

2026-09-02

Grade Changed

Trust grade D → C

2026-09-02

Rank Moved

Rank rose 545 spots (#1227 → #682)

2026-09-02

HVTrust Changed

HVTrust up 29.2pts (21.8 → 51.0)

2026-09-01

Rank Moved

Rank dropped 27 spots (#1200 → #1227)

2026-08-31

Rank Moved

Rank dropped 19 spots (#1181 → #1200)

2026-08-30

Rank Moved

Rank dropped 32 spots (#1149 → #1181)

2026-08-29

Rank Moved

Rank dropped 27 spots (#1122 → #1149)

2026-08-28

Rank Moved

Rank dropped 26 spots (#1096 → #1122)

2026-08-27

Rank Moved

Rank dropped 21 spots (#1075 → #1096)

2026-08-26

Rank Moved

Rank dropped 77 spots (#998 → #1075)

2026-08-22

Rank Moved

Rank rose 82 spots (#1081 → #999)

2026-08-22

Activity Score Changed

Activity score up 9pts (61 → 71)

2026-08-16

Rank Moved

Rank dropped 34 spots (#1050 → #1084)

2026-08-14

Rank Moved

Rank dropped 45 spots (#1007 → #1052)

2026-08-14

Activity Score Changed

Activity score down 6pts (68 → 62)

2026-08-13

Rank Moved

Rank dropped 23 spots (#984 → #1007)

2026-08-10

Rank Moved

Rank dropped 81 spots (#899 → #980)

2026-08-08

Rank Moved

Rank dropped 407 spots (#470 → #877)

2026-08-06

Newly Listed

First tracked at rank #470

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/openocta.svg)](https://hvtracker.net/agents/openocta)
            
HTML:
            <a href="https://hvtracker.net/agents/openocta"><img src="https://hvtracker.net/badge/openocta.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