Is ARTEMIS safe to use?

ARTEMIS has an HVTrust score of 26.4/100 (Grade D), ranked #1319 of 1343 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for ARTEMIS?

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

ARTEMIS

Repository by google

ARTEMIS turns natural-language instructions into reliable Android automation. It automates end-to-end workflows, captures logs, and integrates seamlessly with AI coding assistants such as Antigravity, Codex, and Claude Code. It also achieves 99%+ success rate on AndroidWorld Benchmark.

Browser & Computer Use Python Listed Apache-2.0

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

OSSF Scorecard No result

Provenance None

Signed commits 5%

Last push today

Compare ARTEMIS

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

Pick any agent to compare →

Suggest a correction

In detail: ARTEMIS scores 26.4/100 (Grade D), ranked #1319 of 1343 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; 5% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How ARTEMIS 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 to 9.0no OSSF Scorecard result yet +43.2 → 69.6 B · #13 of 43
Sign every commit5% signed today +2.4 → 28.8 D · #41 of 43

Already done? Suggest a correction Add the trust badge

How ARTEMIS compares in Browser & Computer Use

Bars show each HVTrust score; the tick marks ARTEMIS’s 26.4.

Where the 26.4 comes from

HVTrust dimensions vs the Browser & Computer Use average

26.4 / 100 · 50.0% confidence

ARTEMIS Browser & Computer Use average (43 agents)

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

0.3 / 25

9.1 below avg 9.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.5 below avg 12.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.3 below avg 11.8

Maintenance60% last-push freshness · 40% commit activity

19.5 / 20

6.1 above avg 13.4

AdoptionLog-scaled stars · package downloads

9.7 / 20

1.6 below avg 11.3

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-09-29

Newly Listed

First tracked at rank #1319

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

86.6

Activity sub-score · out of 100

#41

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 →

Activity & Reach

Stars

10.6k

Forks

1.1k

Last Push

2026-09-29

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

NEW

Analysis

Activity Inputs

86.6 / 100

StarsRepository reach

24.2 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

23.3 / 25

CommunityFork signal

14.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

Common questions about ARTEMIS

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

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

Does ARTEMIS have an OpenSSF Scorecard?

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

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

What license does ARTEMIS use?

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

Are ARTEMIS's commits signed?

5% of the last 100 commits to ARTEMIS 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

high confidence

Implemented

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

Google Gemini

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

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

For maintainers

HVTrust scores ARTEMIS 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-29

Newly Listed

First tracked at rank #1319

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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