updated 2026-08-09 19:31 UTC

TuriX

TurixAI/TuriX-CUA

This is the official website for TuriX Computer-use-Agent

Browser & Computer Use Python Grade D Listed MIT
20.6/100
Rank #975 of 1204
Compare TuriX

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-07-30 · 10d ago
Recent change
Rank +3

Is TuriX safe? TuriX scores 20.6/100 (Grade D), ranked #975 of 1204 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; 3% of recent commits are signed; last pushed 2026-07-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#30 Open Operator — 28.1 (D) → #31 arbigent — 24.4 (D) → #32 openocta — 22.2 (D) → #33 openyak — 21.4 (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-08
Rank Moved
Rank dropped 484 spots (#485 → #969)
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, Google Gemini
2026-08-06
Rank Moved
Rank dropped 33 spots (#458 → #491)
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.
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 TuriX View Browser & Computer Use Report missing data
65.0
Activity sub-score · out of 100
#34
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 →

Signals refreshed 2026-08-09 19:31 UTC · Repo last pushed 10 days ago

Activity & Reach

Stars
3.1k
Forks
333
Last Push
2026-07-30
10 days ago
Commits (4 wk)
4
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
4
Rank Change
▼6
was #969

Analysis

HVTrust Dimensions vs Browser & Computer Use

20.6 / 100 · 50.0% confidence

TuriX Browser & Computer Use average (34 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.1 / 25
7.7 below avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.7 below avg 11.2
Maintenance60% last-push freshness · 40% commit activity
14.1 / 20
2.1 above avg 12.0
AdoptionLog-scaled stars · package downloads
8.4 / 20
2.4 below avg 10.8

Activity Inputs

65.0 / 100
StarsRepository reach
21.0 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
11.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
3%
of last 100 commits verified

Is TuriX safe?

Public trust evidence for TuriX 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 TuriX publish package provenance?
No published build provenance is currently detected for TuriX. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does TuriX have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for TuriX. 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 TuriX actively maintained?
Maintained. Last push was 10 days ago.
What license does TuriX use?
TuriX ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are TuriX's commits signed?
3% of the last 100 commits to TuriX 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
low 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
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium 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 TuriX'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-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, Google Gemini

Maintain TuriX?

For maintainers

HVTrust scores TuriX 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
Rank 8Listed 1Score 1Surface 1
2026-08-08
Rank Moved
Rank dropped 484 spots (#485 → #969)
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, Google Gemini
2026-08-06
Rank Moved
Rank dropped 33 spots (#458 → #491)
2026-08-03
Rank Moved
Rank dropped 19 spots (#439 → #458)
2026-07-28
Rank Moved
Rank dropped 19 spots (#418 → #437)
2026-07-20
Activity Score Changed
Activity score up 12pts (52 → 64)
2026-07-14
Rank Moved
Rank dropped 46 spots (#371 → #417)
2026-07-13
Rank Moved
Rank dropped 40 spots (#331 → #371)
2026-06-24
Rank Moved
Rank dropped 21 spots (#296 → #317)
2026-06-21
Rank Moved
Rank dropped 29 spots (#256 → #285)
2026-06-20
Newly Listed
First tracked at rank #256
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 20.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/turix.svg)](https://hvtracker.net/agents/turix)
HTML:
<a href="https://hvtracker.net/agents/turix"><img src="https://hvtracker.net/badge/turix.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.2 · Raw JSON