updated 2026-11-11 00:08 UTC

Mika

Repository Website

An on-device AI agent for Android that operates apps and the web to get things done for you.

Browser & Computer Use Kotlin Listed Apache-2.0

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

OSSF Scorecard No result
Provenance None
Signed commits 0%
Last push yesterday
Compare Mika

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

Pick any agent to compare →
Suggest a correction

In detail: Mika scores 24.3/100 (Grade D), ranked #1368 of 1387 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; recent commits are unsigned; last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mika 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Mika 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.

  1. Source Unsigned

    github.com/wangzan101/Mika, Apache-2.0, last pushed 2026-11-10. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Not checked

    No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.

  3. Published packages None

    No registry package. Mika 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 Mika.

Evidence behind this score

Coverage D: 1 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks (missing)
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Mika’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.

Signed credential (JSON) How to verify

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 Mika compares in Browser & Computer Use

  1. #44 PyWinAssistant 29.5 +5.2
  2. #45 ESP32 iPhone Agent 26.6 +2.3
  3. #46 Mika 24.3 this agent
  4. #47 Open Operator 22.6 −1.7
  5. #48 typesafe-computer-use 18.9 −5.4

Bars show each HVTrust score; the tick marks Mika’s 24.3.

Where the 24.3 comes from

HVTrust dimensions vs the Browser & Computer Use average

24.3 / 100 · 50.0% confidence

Mika Browser & Computer Use average (48 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
9.9 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.5 above avg 12.4
AdoptionLog-scaled stars · package downloads
9.4 / 20
1.6 below avg 11.0

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-11-10
Newly Listed
First tracked at rank #1368
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
View Browser & Computer Use Report missing data
88.6
Activity sub-score · out of 100
#46
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 →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed yesterday

Activity & Reach

Stars
8.1k
Forks
1.8k
Last Push
2026-11-10
yesterday
Commits (4 wk)
675
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
75
Rank Change
=
was #1368

Analysis

Activity Inputs

88.6 / 100
StarsRepository reach
23.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.2 / 20

Common questions about Mika

Public trust evidence for Mika 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 Mika publish package provenance?
No published build provenance is currently detected for Mika. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Mika have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Mika. 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 Mika actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Mika use?
Mika ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Mika's commits signed?
0% of the last 100 commits to Mika 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
Declared
MCP support appears present, but direct server implementation is less certain.
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
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 Mika?

For maintainers

HVTrust scores Mika 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
Listed 1
2026-11-10
Newly Listed
First tracked at rank #1368
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 24.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/mika.svg)](https://hvtracker.net/agents/mika)
HTML:
<a href="https://hvtracker.net/agents/mika"><img src="https://hvtracker.net/badge/mika.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