Is autoMate safe to use?

autoMate has an HVTrust score of 52.3/100 (Grade C), ranked #419 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for autoMate?

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

autoMate

yuruotong1/autoMate

Like Manus, Computer Use Agent(CUA) and Omniparser, we are computer-using agents.AI-driven local automation assistant th

Browser & Computer Use Python Grade C Listed MIT

52.3/100

Rank #419 of 1204

Compare autoMate

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-08-06 · 3d ago

Recent change

Rank +4

Is autoMate safe? autoMate scores 52.3/100 (Grade C), ranked #419 of 1204 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 3.0/10; 67% of recent commits are signed; last pushed 2026-08-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#14 Open Computer Use — 53.3 (C) → #15 UFO — 53.2 (C) → #17 OmniParser — 50.7 (C) → #18 Agent-S — 48.6 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-08

Rank Moved

Rank dropped 103 spots (#313 → #416)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, Google Gemini, OpenAI

Maintainer Checklist

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

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

62.6

Activity sub-score · out of 100

#16

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 →

Activity & Reach

Stars

3.9k

Forks

494

Last Push

2026-08-06

3 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #416

Analysis

HVTrust Dimensions vs Browser & Computer Use

52.3 / 100 · 100.0% confidence

autoMate Browser & Computer Use average (34 agents)

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

7.1 / 25

0.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

11.1 / 17

in line with avg 11.2

Maintenance60% last-push freshness · 40% commit activity

13.0 / 20

1.0 above avg 12.0

AdoptionLog-scaled stars · package downloads

8.6 / 20

2.2 below avg 10.8

Activity Inputs

62.6 / 100

StarsRepository reach

21.6 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

12.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.0 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

67%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 3

Is autoMate safe?

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

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

Does autoMate have an OpenSSF Scorecard?

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

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

What license does autoMate use?

autoMate ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are autoMate's commits signed?

67% of the last 100 commits to autoMate 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

autoMate appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high 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 autoMate'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

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, Google Gemini, OpenAI

2026-08-07

Activity Resumed

Activity resumed

2026-07-29

Activity Went Stale

No commits for 90 days

Maintain autoMate?

For maintainers

HVTrust scores autoMate 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-08

Rank Moved

Rank dropped 103 spots (#313 → #416)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, Google Gemini, OpenAI

2026-08-07

Activity Resumed

Activity resumed

2026-08-07

Activity Score Changed

Activity score up 17pts (46 → 63)

2026-07-29

Activity Went Stale

No commits for 90 days

2026-07-29

Rank Moved

Rank dropped 12 spots (#342 → #354)

2026-07-15

Rank Moved

Rank dropped 25 spots (#305 → #330)

2026-07-14

Rank Moved

Rank dropped 18 spots (#287 → #305)

2026-07-13

Rank Moved

Rank dropped 33 spots (#254 → #287)

2026-06-24

Rank Moved

Rank dropped 34 spots (#209 → #243)

2026-06-23

Rank Moved

Rank dropped 15 spots (#194 → #209)

2026-06-21

Scorecard Added

OSSF Scorecard: 4.0/10

2026-06-21

Rank Moved

Rank rose 73 spots (#258 → #185)

2026-06-21

HVTrust Changed

HVTrust up 28.1pts (20.0 → 48.1)

2026-06-20

Newly Listed

First tracked at rank #258

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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