Is arbigent safe to use?

arbigent has an HVTrust score of 59.3/100 (Grade C), ranked #634 of 1328 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 59.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 645 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 C Listed Apache-2.0

59.3/100

Rank #634 of 1328

Compare arbigent

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-17 · 3d ago

Recent change

Rank

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

Ranked neighbours in Browser & Computer Use

#16 AIHawk — 63.3 (C) → #17 UFO — 61.2 (C) → #19 openyak — 58.5 (C) → #20 BrowserGym agents — 57.6 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-18

Rank Moved

Rank rose 12 spots (#647 → #635)

2026-09-11

Rank Moved

Rank dropped 12 spots (#631 → #643)

2026-09-09

Rank Moved

Rank rose 14 spots (#637 → #623)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.4/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 arbigent View Browser & Computer Use Report missing data

74.9

Activity sub-score · out of 100

#18

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

645

Forks

Last Push

2026-09-17

3 days ago

Commits (4 wk)

123

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #631

Analysis

HVTrust Dimensions vs Browser & Computer Use

59.3 / 100 · 100.0% confidence

arbigent Browser & Computer Use average (42 agents)

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

7.9 / 25

1.7 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

13.1 / 17

1.2 above avg 11.9

Maintenance60% last-push freshness · 40% commit activity

19.8 / 20

6.6 above avg 13.2

AdoptionLog-scaled stars · package downloads

6.7 / 20

4.6 below avg 11.3

Activity Inputs

74.9 / 100

StarsRepository reach

16.9 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

8.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.4 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

23%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 4

SAST 10

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Is arbigent safe?

arbigent has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

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

Actively maintained. The repository was pushed to within the last 3 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?

23% 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-09-18

Rank Moved

Rank rose 12 spots (#647 → #635)

2026-09-11

Rank Moved

Rank dropped 12 spots (#631 → #643)

2026-09-09

Rank Moved

Rank rose 14 spots (#637 → #623)

2026-09-07

Rank Moved

Rank dropped 35 spots (#596 → #631)

2026-09-05

Rank Moved

Rank dropped 69 spots (#523 → #592)

2026-09-04

Rank Moved

Rank dropped 24 spots (#499 → #523)

2026-09-03

Rank Moved

Rank dropped 31 spots (#468 → #499)

2026-09-02

Rank Moved

Rank dropped 15 spots (#453 → #468)

2026-08-31

Rank Moved

Rank rose 12 spots (#461 → #449)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.3/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 591 spots (#1056 → #465)

2026-08-29

HVTrust Changed

HVTrust up 33.3pts (23.3 → 56.6)

2026-08-28

Rank Moved

Rank dropped 30 spots (#1026 → #1056)

2026-08-27

Rank Moved

Rank dropped 23 spots (#1003 → #1026)

2026-08-26

Rank Moved

Rank dropped 87 spots (#916 → #1003)

2026-08-25

Rank Moved

Rank rose 13 spots (#929 → #916)

2026-08-24

Rank Moved

Rank dropped 13 spots (#916 → #929)

2026-08-22

Rank Moved

Rank dropped 14 spots (#903 → #917)

2026-08-21

Rank Moved

Rank dropped 33 spots (#870 → #903)

2026-08-21

Activity Score Changed

Activity score down 6pts (74 → 69)

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