Is TuriX safe to use?

TuriX has an HVTrust score of 41.5/100 (Grade D), ranked #1182 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for TuriX?

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

TuriX

Repository Website

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

Browser & Computer Use Python Listed MIT

Is TuriX safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.0 / 10

Provenance None

Signed commits 3%

Last push 34d ago

Compare TuriX

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

Pick any agent to compare →

Suggest a correction

In detail: TuriX scores 41.5/100 (Grade D), ranked #1182 of 1378 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.0/10; 3% of recent commits are signed; last pushed 2026-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How TuriX could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 2.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +14.6 → 56.1 C · #25 of 45
Sign every commit3% signed today +4.8 → 46.3 D · #34 of 45

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships TuriX and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/TurixAI/TuriX-CUA, MIT, last pushed 2026-09-14. 3% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.0/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 5

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0
Published packages None

No registry package. TuriX is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-10-16 OSSF Scorecard: 2.0/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues TuriX’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How TuriX compares in Browser & Computer Use

Bars show each HVTrust score; the tick marks TuriX’s 41.5.

Where the 41.5 comes from

HVTrust dimensions vs the Browser & Computer Use average

41.5 / 100 · 100.0% confidence

TuriX Browser & Computer Use average (45 agents)

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

2.7 / 25

7.5 below avg 10.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.9 below avg 12.7

Transparency50% declared license · 50% OSSF Scorecard

10.2 / 17

1.8 below avg 12.0

Maintenance60% last-push freshness · 40% commit activity

9.7 / 20

3.1 below avg 12.8

AdoptionLog-scaled stars · package downloads

8.4 / 20

2.7 below avg 11.1

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-16

Scorecard Added

OSSF Scorecard: 2.0/10

2026-10-16

Rank Moved

Rank rose 196 spots (#1375 → #1179)

2026-10-16

HVTrust Changed

HVTrust up 23.2pts (18.5 → 41.7)

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 34 days ago. Fresh activity helps separate stable projects from stale ones.

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

53.1

Activity sub-score · out of 100

#36

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 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-09-29 2026-10-17

Activity & Reach

Stars

3.2k

Forks

330

Last Push

2026-09-14

34 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1181

Analysis

Activity Inputs

53.1 / 100

StarsRepository reach

21.0 / 30

FreshnessLast push recency

20.3 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.7 / 20

Common questions about TuriX

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?

TuriX has an OpenSSF Scorecard score of 2.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 TuriX actively maintained?

Slowing down. Last push was 34 days ago — keep an eye on whether activity resumes.

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.

OpenAI

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

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

2026-10-16

Scorecard Added

OSSF Scorecard: 2.0/10

2026-10-16

Rank Moved

Rank rose 196 spots (#1375 → #1179)

2026-10-16

HVTrust Changed

HVTrust up 23.2pts (18.5 → 41.7)

2026-10-14

Activity Score Changed

Activity score down 6pts (60 → 54)

2026-10-09

Rank Moved

Rank dropped 25 spots (#1342 → #1367)

2026-09-23

Rank Moved

Rank dropped 139 spots (#1181 → #1320)

2026-09-22

Rank Moved

Rank dropped 744 spots (#437 → #1181)

2026-09-21

Rank Moved

Rank rose 885 spots (#1322 → #437)

2026-09-14

Activity Score Changed

Activity score up 12pts (52 → 64)

2026-09-03

Rank Moved

Rank dropped 10 spots (#1289 → #1299)

2026-09-02

Rank Moved

Rank dropped 16 spots (#1273 → #1289)

2026-09-01

Rank Moved

Rank dropped 14 spots (#1259 → #1273)

2026-08-31

Rank Moved

Rank dropped 12 spots (#1247 → #1259)

2026-08-30

Rank Moved

Rank dropped 13 spots (#1234 → #1247)

2026-08-29

Rank Moved

Rank dropped 45 spots (#1189 → #1234)

2026-08-29

Activity Score Changed

Activity score down 6pts (60 → 54)

2026-08-28

Rank Moved

Rank dropped 17 spots (#1172 → #1189)

2026-08-27

Rank Moved

Rank dropped 15 spots (#1157 → #1172)

2026-08-26

Rank Moved

Rank dropped 55 spots (#1102 → #1157)

2026-08-24

Rank Moved

Rank dropped 12 spots (#1086 → #1098)

2026-08-19

Rank Moved

Rank dropped 22 spots (#1062 → #1084)

2026-08-17

Rank Moved

Rank rose 14 spots (#1071 → #1057)

2026-08-16

Rank Moved

Rank dropped 37 spots (#1034 → #1071)

2026-08-10

Rank Moved

Rank dropped 55 spots (#980 → #1035)

2026-08-08

Rank Moved

Rank dropped 484 spots (#485 → #969)

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)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

TuriX

How TuriX could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How TuriX compares in Browser & Computer Use

Where the 41.5 comes from

HVTrust dimensions vs the Browser & Computer Use average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about TuriX

AI agent surface

Maintain TuriX?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Browser & Computer Use