Is MiMo Code safe to use?

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

What is the trust score for MiMo Code?

MiMo Code scores 25.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 13.6k GitHub stars and is categorized under Coding Agents.

MiMo Code

Repository

Website

MiMo Code: Where Models and Agents Co-Evolve

Coding Agents TypeScript Listed MIT

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

OSSF Scorecard No result

Provenance None

Signed commits 71%

Last push today

Compare MiMo Code

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Suggest a correction

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

How MiMo Code 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 +45.3 → 70.5 B · #18 of 75
Sign every commit71% signed today +0.8 → 26.0 D · #73 of 75

Already done? Suggest a correction Add the trust badge

How MiMo Code compares in Coding Agents

Bars show each HVTrust score; the tick marks MiMo Code’s 25.2.

Where the 25.2 comes from

HVTrust dimensions vs the Coding Agents average

25.2 / 100 · 50.0% confidence

MiMo Code Coding Agents average (75 agents)

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

3.5 / 25

5.5 below avg 9.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.0 below avg 11.8

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.2 below avg 11.7

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.1 above avg 14.9

AdoptionLog-scaled stars · package downloads

9.9 / 20

2.3 below avg 12.2

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 #1326

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.

Compare with another agent Get email alerts for MiMo Code View Coding Agents Report missing data

89.4

Activity sub-score · out of 100

#73

In Coding Agents

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

13.6k

Forks

1.4k

Last Push

2026-09-29

today

Commits (4 wk)

164

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

818

Rank Change

NEW

Analysis

Activity Inputs

89.4 / 100

StarsRepository reach

24.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

14.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

71%

of last 100 commits verified

Common questions about MiMo Code

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

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

Does MiMo Code have an OpenSSF Scorecard?

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

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

What license does MiMo Code use?

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

Are MiMo Code's commits signed?

71% of the last 100 commits to MiMo Code 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

MiMo Code appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

6 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

code

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 MiMo Code?

For maintainers

HVTrust scores MiMo Code 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 #1326

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Coding Agents

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