updated 2026-11-05 12:09 UTC

MiroThinker

Repository Website by MiroMindAI

MiroThinker is a deep research agent optimized for complex research and prediction tasks. Our latest models, MiroThinker-1.7, achieves 74.0 and 75.3 on the BrowseComp and BrowseComp Zh, respectively.

Research & Data Python Listed Apache-2.0

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

OSSF Scorecard 3.0 / 10
Provenance None
Signed commits 49%
Last push 122d ago
Compare MiroThinker

How does it stack up against its Research & Data neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MiroThinker scores 39.8/100 (Grade D), ranked #1210 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.0/10; 49% of recent commits are signed; last pushed 2026-07-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How MiroThinker 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 MiroThinker 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 Partly signed

    github.com/MiroMindAI/MiroThinker, Apache-2.0, last pushed 2026-07-06. 49% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.0/10 (scanned Oct 31, 2026). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 4
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

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

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues MiroThinker’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 MiroThinker compares in Research & Data

  1. #25 luxas 47.6 +7.8
  2. #26 FinnewsHunter 44.9 +5.1
  3. #27 MiroThinker 39.8 this agent
  4. #28 Sotopia agents 38.2 −1.6
  5. #29 deep-research 36.0 −3.8

Bars show each HVTrust score; the tick marks MiroThinker’s 39.8.

Where the 39.8 comes from

HVTrust dimensions vs the Research & Data average

39.8 / 100 · 100.0% confidence

MiroThinker Research & Data average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.2 / 25
2.5 below avg 8.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
0.8 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
3.9 / 20
9.5 below avg 13.4
AdoptionLog-scaled stars · package downloads
9.4 / 20
1.4 below avg 10.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/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 122 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View Research & Data Report missing data
44.9
Activity sub-score · out of 100
#27
In Research & Data

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

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed 122 days ago

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
8.4k
Forks
648
Last Push
2026-07-06
122 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
▲4
was #1214

Analysis

Activity Inputs

44.9 / 100
StarsRepository reach
23.6 / 30
FreshnessLast push recency
8.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.1 / 20

Common questions about MiroThinker

Public trust evidence for MiroThinker 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 MiroThinker publish package provenance?
No published build provenance is currently detected for MiroThinker. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MiroThinker have an OpenSSF Scorecard?
MiroThinker has an OpenSSF Scorecard score of 3.0/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 MiroThinker actively maintained?
Slowing down. Last push was 122 days ago — keep an eye on whether activity resumes.
What license does MiroThinker use?
MiroThinker ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MiroThinker's commits signed?
49% of the last 100 commits to MiroThinker 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
MiroThinker appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
2 tags
Broad capability areas detected.
  • browser
  • database
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 MiroThinker'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-10-04
Activity Went Stale
No commits for 90 days

Maintain MiroThinker?

For maintainers

HVTrust scores MiroThinker 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
Rank 24Stale 1
2026-10-04
Activity Went Stale
No commits for 90 days
2026-09-23
Rank Moved
Rank dropped 633 spots (#478 → #1111)
2026-09-22
Rank Moved
Rank dropped 104 spots (#374 → #478)
2026-09-21
Rank Moved
Rank rose 732 spots (#1106 → #374)
2026-09-12
Rank Moved
Rank dropped 11 spots (#1083 → #1094)
2026-09-11
Rank Moved
Rank dropped 10 spots (#1073 → #1083)
2026-09-09
Rank Moved
Rank dropped 13 spots (#1062 → #1075)
2026-09-08
Rank Moved
Rank dropped 10 spots (#1052 → #1062)
2026-09-07
Rank Moved
Rank dropped 36 spots (#1016 → #1052)
2026-09-06
Rank Moved
Rank dropped 12 spots (#1004 → #1016)
2026-09-05
Rank Moved
Rank dropped 50 spots (#954 → #1004)
2026-09-04
Rank Moved
Rank dropped 32 spots (#922 → #954)
2026-09-03
Rank Moved
Rank dropped 47 spots (#875 → #922)
2026-09-02
Rank Moved
Rank dropped 49 spots (#826 → #875)
2026-09-01
Rank Moved
Rank dropped 30 spots (#796 → #826)
2026-08-31
Rank Moved
Rank dropped 33 spots (#763 → #796)
2026-08-30
Rank Moved
Rank dropped 29 spots (#734 → #763)
2026-08-29
Rank Moved
Rank dropped 49 spots (#685 → #734)
2026-08-28
Rank Moved
Rank dropped 21 spots (#664 → #685)
2026-08-27
Rank Moved
Rank dropped 22 spots (#642 → #664)
2026-08-26
Rank Moved
Rank dropped 101 spots (#541 → #642)
2026-08-24
Rank Moved
Rank dropped 16 spots (#527 → #543)
2026-08-22
Rank Moved
Rank rose 12 spots (#539 → #527)
2026-08-10
Rank Moved
Rank dropped 17 spots (#495 → #512)
2026-08-08
Rank Moved
Rank dropped 133 spots (#358 → #491)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 39.8 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/mirothinker.svg)](https://hvtracker.net/agents/mirothinker)
HTML:
<a href="https://hvtracker.net/agents/mirothinker"><img src="https://hvtracker.net/badge/mirothinker.svg" alt="HVTrust"></a>

Other agents in Research & Data

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