Is arbigent safe to use?

arbigent has an HVTrust score of 24.5/100 (Grade D), ranked #861 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for arbigent?

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

arbigent

takahirom/arbigent

AI Agent for testing Android, iOS, and Web apps. Get Started in 5 Minutes. Arbigent's intuitive UI and powerful code int

Browser & Computer Use Kotlin Grade D Listed Apache-2.0

24.5/100

Rank #861 of 1308

Compare arbigent

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-19 · 0d ago

Recent change

Rank +2

Is arbigent safe? arbigent scores 24.5/100 (Grade D), ranked #861 of 1308 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; 17% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#36 Open Operator — 27.5 (D) → #37 Obscura — 26.9 (D) → #39 openyak — 21.3 (D) → #40 TuriX — 20.3 (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-18

Rank Moved

Rank rose 12 spots (#872 → #860)

2026-08-16

Rank Moved

Rank dropped 20 spots (#858 → #878)

2026-08-13

Rank Moved

Rank dropped 11 spots (#848 → #859)

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 arbigent View Browser & Computer Use Report missing data

75.1

Activity sub-score · out of 100

#38

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 →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

630

Forks

Last Push

2026-08-19

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #860

Analysis

HVTrust Dimensions vs Browser & Computer Use

24.5 / 100 · 50.0% confidence

arbigent Browser & Computer Use average (41 agents)

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

0.9 / 25

6.5 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.2 below avg 10.7

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.0 above avg 13.0

AdoptionLog-scaled stars · package downloads

6.7 / 20

4.5 below avg 11.2

Activity Inputs

75.1 / 100

StarsRepository reach

16.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

24.9 / 25

CommunityFork signal

8.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

17%

of last 100 commits verified

Is arbigent safe?

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

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

Does arbigent have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for arbigent. 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 arbigent actively maintained?

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

What license does arbigent use?

arbigent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are arbigent's commits signed?

17% of the last 100 commits to arbigent 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

Implemented

arbigent appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

OpenAI

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

For maintainers

HVTrust scores arbigent 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-18

Rank Moved

Rank rose 12 spots (#872 → #860)

2026-08-16

Rank Moved

Rank dropped 20 spots (#858 → #878)

2026-08-13

Rank Moved

Rank dropped 11 spots (#848 → #859)

2026-08-10

Rank Moved

Rank dropped 44 spots (#802 → #846)

2026-08-08

Rank Moved

Rank dropped 349 spots (#449 → #798)

2026-08-06

Newly Listed

First tracked at rank #483

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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