OmniParser
A simple screen parsing tool towards pure vision based GUI agent
Is OmniParser safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare OmniParser
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →In detail: OmniParser scores 44.9/100 (Grade D), ranked #1096 of 1371 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.4/10; 13% of recent commits are signed; last pushed 2026-07-20. Every point is earned from checkable signals — never paid placement. How scoring works →
How OmniParser 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 from 4.4 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Fuzzing 0 +9.6 → 54.5 C · #26 of 45
- Sign every commit13% signed today +4.3 → 49.2 D · #33 of 45
Chain of custody
Scanners check what the code says. This traces who ships OmniParser and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/microsoft/OmniParser, CC-BY-4.0, last pushed 2026-07-20. 13% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.4/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection6
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 6CI-Tests 5CII-Best-Practices 0Code-Review 1Contributors 10Dangerous-Workflow -1Dependency-Update-Tool 0Fuzzing 0License 10Maintained 2Packaging -1Pinned-Dependencies 0SAST 5Security-Policy 10Signed-Releases -1Token-Permissions -1Vulnerabilities 7 -
Published packages None
No registry package. OmniParser is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of OmniParser.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues OmniParser’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How OmniParser compares in Browser & Computer Use
- #33 bb-browser 48.1 +3.2
- #34 openocta 46.5 +1.6
- #35 OmniParser 44.9 this agent
- #36 MolmoWeb 41.5 −3.4
- #37 UI-TARS 41.0 −3.9
Bars show each HVTrust score; the tick marks OmniParser’s 44.9.
Where the 44.9 comes from
HVTrust dimensions vs the Browser & Computer Use average
44.9 / 100 · 100.0% confidenceOmniParser Browser & Computer Use average (45 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
55.8 / 100Common questions about OmniParser
Does OmniParser publish package provenance?
Does OmniParser have an OpenSSF Scorecard?
Is OmniParser actively maintained?
What license does OmniParser use?
Are OmniParser's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/omniparser)
<a href="https://hvtracker.net/agents/omniparser"><img src="https://hvtracker.net/badge/omniparser.svg" alt="HVTrust"></a>
Other agents in Browser & Computer Use
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.4 · Raw JSON