Is OmniParser safe to use?

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

What is the trust score for OmniParser?

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

OmniParser

microsoft/OmniParser

A simple screen parsing tool towards pure vision based GUI agent

Browser & Computer Use Jupyter Notebook Grade D Listed CC-BY-4.0

47.7/100

Rank #490 of 1308

Compare OmniParser

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 B · 3/5 signals

Last push

2026-07-20 · 36d ago

Recent change

Rank +2

Is OmniParser safe? OmniParser scores 47.7/100 (Grade D), ranked #490 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 12% of recent commits are signed; last pushed 2026-07-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#18 Open Computer Use — 51.4 (C) → #19 autoMate — 51.2 (C) → #21 Agent-S — 46.8 (D) → #22 Nanobrowser — 46.6 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-24

Rank Moved

Rank dropped 13 spots (#477 → #490)

2026-08-22

Rank Moved

Rank rose 12 spots (#492 → #480)

2026-08-19

Rank Moved

Rank dropped 31 spots (#460 → #491)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/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 36 days ago. Fresh activity helps separate stable projects from stale ones.

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

62.0

Activity sub-score · out of 100

#20

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

25.3k

Forks

2.2k

Last Push

2026-07-20

36 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

Open Issues

173

Rank Change

was #490

Analysis

HVTrust Dimensions vs Browser & Computer Use

47.7 / 100 · 100.0% confidence

OmniParser Browser & Computer Use average (41 agents)

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

6.0 / 25

1.5 below avg 7.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.6 below avg 12.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

1.4 above avg 10.8

Maintenance60% last-push freshness · 40% commit activity

9.6 / 20

3.2 below avg 12.8

AdoptionLog-scaled stars · package downloads

10.6 / 20

0.7 below avg 11.3

Activity Inputs

62.0 / 100

StarsRepository reach

26.4 / 30

FreshnessLast push recency

20.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

15.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Aug 24, 2026

Signed Commits

12%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 5

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 1

Packaging -1

Pinned-Dependencies 0

SAST 5

Security-Policy 10

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 7

Is OmniParser safe?

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

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

Does OmniParser have an OpenSSF Scorecard?

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

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

What license does OmniParser use?

OmniParser ships under CC-BY-4.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are OmniParser's commits signed?

12% of the last 100 commits to OmniParser 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

4 detected

Public provider/service dependencies detected.

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

How this surface has changed

Detected changes to OmniParser'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-07-18

Activity Resumed

Activity resumed

2026-07-12

Activity Went Stale

No commits for 90 days

Maintain OmniParser?

For maintainers

HVTrust scores OmniParser 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-24

Rank Moved

Rank dropped 13 spots (#477 → #490)

2026-08-22

Rank Moved

Rank rose 12 spots (#492 → #480)

2026-08-19

Rank Moved

Rank dropped 31 spots (#460 → #491)

2026-08-17

Grade Changed

Trust grade C → D

2026-08-13

Rank Moved

Rank dropped 15 spots (#436 → #451)

2026-08-12

Rank Moved

Rank rose 15 spots (#451 → #436)

2026-08-10

Rank Moved

Rank dropped 16 spots (#432 → #448)

2026-08-08

Rank Moved

Rank dropped 108 spots (#322 → #430)

2026-07-20

Grade Changed

Trust grade D → C

2026-07-20

Rank Moved

Rank rose 23 spots (#310 → #287)

2026-07-20

Activity Score Changed

Activity score up 6pts (67 → 73)

2026-07-18

Activity Resumed

Activity resumed

2026-07-18

Rank Moved

Rank rose 35 spots (#340 → #305)

2026-07-18

HVTrust Changed

HVTrust up 6.3pts (43.5 → 49.8)

2026-07-18

Activity Score Changed

Activity score up 13pts (54 → 67)

2026-07-15

Rank Moved

Rank dropped 25 spots (#316 → #341)

2026-07-14

Rank Moved

Rank dropped 16 spots (#300 → #316)

2026-07-13

Rank Moved

Rank dropped 36 spots (#264 → #300)

2026-07-12

Activity Went Stale

No commits for 90 days

2026-06-24

Rank Moved

Rank dropped 31 spots (#224 → #255)

2026-06-23

Rank Moved

Rank dropped 17 spots (#207 → #224)

2026-06-21

Rank Moved

Rank dropped 12 spots (#186 → #198)

2026-06-18

Rank Moved

Rank dropped 14 spots (#166 → #180)

2026-06-01

Rank Moved

Rank dropped 17 spots (#115 → #132)

2026-05-29

HVTrust Changed

HVTrust up 9.8pts (37.6 → 47.4)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/omniparser.svg)](https://hvtracker.net/agents/omniparser)
            
HTML:
            <a href="https://hvtracker.net/agents/omniparser"><img src="https://hvtracker.net/badge/omniparser.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON