Is MiroFish safe to use?

MiroFish has an HVTrust score of 51.6/100 (Grade C), ranked #897 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MiroFish?

MiroFish scores 51.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 74.8k GitHub stars and is categorized under Multi-Agent Systems.

MiroFish

666ghj/MiroFish

A Simple and Universal Swarm Intelligence Engine, Predicting Anything. 简洁通用的群体智能引擎，预测万物

Multi-Agent Systems Python Listed AGPL-3.0

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

OSSF Scorecard 3.7 / 10

Provenance None

Signed commits 27%

Last push 10d ago

Compare MiroFish

How does it stack up against its Multi-Agent Systems neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MiroFish scores 51.6/100 (Grade C), ranked #897 of 1325 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.7/10; 27% of recent commits are signed; last pushed 2026-09-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How MiroFish compares in Multi-Agent Systems

Bars show each HVTrust score; the tick marks MiroFish’s 51.6.

Where the 51.6 comes from

HVTrust dimensions vs the Multi-Agent Systems average

51.6 / 100 · 100.0% confidence

MiroFish Multi-Agent Systems average (38 agents)

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

6.0 / 25

2.4 below avg 8.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 11.2

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

0.5 below avg 12.1

Maintenance60% last-push freshness · 40% commit activity

12.5 / 20

in line with avg 12.4

AdoptionLog-scaled stars · package downloads

11.7 / 20

1.6 above avg 10.1

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-25

Rank Moved

Rank dropped 13 spots (#882 → #895)

2026-09-24

Rank Moved

Rank rose 15 spots (#897 → #882)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.7/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.

Compare with another agent Get email alerts for MiroFish View Multi-Agent Systems Report missing data

75.5

Activity sub-score · out of 100

#25

In Multi-Agent Systems

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

74.8k

Forks

11.5k

Last Push

2026-09-16

10 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #895

Analysis

Activity Inputs

75.5 / 100

StarsRepository reach

29.2 / 30

FreshnessLast push recency

23.6 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

18.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

27%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about MiroFish

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

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

Does MiroFish have an OpenSSF Scorecard?

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

Maintained. Last push was 10 days ago.

What license does MiroFish use?

MiroFish ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MiroFish's commits signed?

27% of the last 100 commits to MiroFish 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

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: API keys or service config markers documented.

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 MiroFish'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-09-23

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

Maintain MiroFish?

For maintainers

HVTrust scores MiroFish 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-25

Rank Moved

Rank dropped 13 spots (#882 → #895)

2026-09-24

Rank Moved

Rank rose 15 spots (#897 → #882)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: OpenAI

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 423 spots (#474 → #897)

2026-09-23

HVTrust Changed

HVTrust up 8.2pts (43.0 → 51.2)

2026-09-22

Newly Listed

First tracked at rank #474

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank dropped 14 spots (#863 → #877)

2026-09-12

Rank Moved

Rank rose 18 spots (#876 → #858)

2026-09-11

Rank Moved

Rank dropped 13 spots (#863 → #876)

2026-09-09

Rank Moved

Rank dropped 19 spots (#844 → #863)

2026-09-08

Rank Moved

Rank dropped 12 spots (#832 → #844)

2026-09-07

Rank Moved

Rank dropped 38 spots (#794 → #832)

2026-09-05

Rank Moved

Rank dropped 61 spots (#725 → #786)

2026-09-04

Rank Moved

Rank dropped 27 spots (#698 → #725)

2026-09-03

Rank Moved

Rank dropped 26 spots (#672 → #698)

2026-09-02

Rank Moved

Rank dropped 52 spots (#620 → #672)

2026-09-02

Activity Score Changed

Activity score down 5pts (82 → 77)

2026-09-01

Rank Moved

Rank dropped 36 spots (#584 → #620)

2026-08-31

Rank Moved

Rank dropped 30 spots (#554 → #584)

2026-08-30

Scorecard Added

OSSF Scorecard: 3.7/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 579 spots (#1133 → #554)

2026-08-30

HVTrust Changed

HVTrust up 30.8pts (22.1 → 52.9)

2026-08-29

Rank Moved

Rank dropped 38 spots (#1095 → #1133)

2026-08-28

Rank Moved

Rank dropped 28 spots (#1067 → #1095)

2026-08-27

Rank Moved

Rank dropped 16 spots (#1051 → #1067)

2026-08-26

Rank Moved

Rank dropped 90 spots (#961 → #1051)

2026-08-25

Rank Moved

Rank rose 42 spots (#1003 → #961)

2026-08-21

Rank Moved

Rank dropped 130 spots (#865 → #995)

2026-08-21

Activity Score Changed

Activity score down 12pts (94 → 82)

2026-08-17

Rank Moved

Rank rose 11 spots (#865 → #854)

2026-08-10

Newly Listed

First tracked at rank #859

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Multi-Agent Systems

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.3 · Raw JSON