Is MindSearch safe to use?

MindSearch has an HVTrust score of 27.5/100 (Grade D), ranked #1354 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MindSearch?

MindSearch scores 27.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.9k GitHub stars and is categorized under Research & Data.

MindSearch

Repository by InternLM

🔍 An LLM-based Multi-agent Framework of Web Search Engine (like Perplexity.ai Pro and SearchGPT)

Research & Data JavaScript Needs review Apache-2.0

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

OSSF Scorecard 2.4 / 10

Provenance None

Signed commits 100%

Last push 474d ago

Compare MindSearch

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

Pick any agent to compare →

Suggest a correction

In detail: MindSearch scores 27.5/100 (Grade D), ranked #1354 of 1378 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 2.4/10; 100% of recent commits are signed; last pushed 2025-07-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How MindSearch 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 2.4 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +13.8 → 41.3 D · #25 of 38

Already done? Suggest a correction Add the trust badge

Chain of custody

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

github.com/InternLM/MindSearch, Apache-2.0, last pushed 2025-07-04. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.4/10 (scanned Oct 18, 2026). The checks that decide who can get a change released:
- Code Review9
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 9

Contributors 6

Dangerous-Workflow -1

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 -1

Vulnerabilities 0
Published packages None

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

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 MindSearch’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 MindSearch compares in Research & Data

Bars show each HVTrust score; the tick marks MindSearch’s 27.5.

Where the 27.5 comes from

HVTrust dimensions vs the Research & Data average

27.5 / 100 · 100.0% confidence

MindSearch Research & Data average (38 agents)

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

8.0 / 25

in line with avg 8.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.1 below avg 11.9

Transparency50% declared license · 50% OSSF Scorecard

10.5 / 17

1.2 below avg 11.7

Maintenance60% last-push freshness · 40% commit activity

0 / 20

13.5 below avg 13.5

AdoptionLog-scaled stars · package downloads

9.2 / 20

1.6 below avg 10.8

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-09

Rank Moved

Rank dropped 12 spots (#1320 → #1332)

2026-09-23

Rank Moved

Rank dropped 440 spots (#861 → #1301)

2026-09-22

Rank Moved

Rank dropped 437 spots (#424 → #861)

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 474 days ago. Fresh activity helps separate stable projects from stale ones.

Review Flags

[4.2.1] no meaningful activity in 12 months (last push 2025-07-04)

Compare with another agent Get email alerts for MindSearch View Research & Data Report missing data

36.3

Activity sub-score · out of 100

#33

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 →

Rank Trend

2026-09-29 2026-10-20

Activity & Reach

Stars

6.9k

Forks

692

Last Push

2025-07-04

474 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #1354

Analysis

Activity Inputs

36.3 / 100

StarsRepository reach

23.1 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

13.2 / 20

Common questions about MindSearch

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

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

Does MindSearch have an OpenSSF Scorecard?

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

Stale. The repository has not been pushed to in 474 days. Consider whether the project is still being maintained.

What license does MindSearch use?

MindSearch ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MindSearch's commits signed?

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

low confidence

None detected

No clear third-party provider dependency detected.

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

Maintain MindSearch?

For maintainers

HVTrust scores MindSearch 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-10-09

Rank Moved

Rank dropped 12 spots (#1320 → #1332)

2026-09-23

Rank Moved

Rank dropped 440 spots (#861 → #1301)

2026-09-22

Rank Moved

Rank dropped 437 spots (#424 → #861)

2026-09-21

Rank Moved

Rank rose 876 spots (#1300 → #424)

2026-09-06

Rank Moved

Rank dropped 11 spots (#1261 → #1272)

2026-09-05

Rank Moved

Rank dropped 15 spots (#1246 → #1261)

2026-09-04

Rank Moved

Rank dropped 17 spots (#1229 → #1246)

2026-09-03

Rank Moved

Rank dropped 42 spots (#1187 → #1229)

2026-09-02

Rank Moved

Rank dropped 38 spots (#1149 → #1187)

2026-09-01

Rank Moved

Rank dropped 41 spots (#1108 → #1149)

2026-08-31

Rank Moved

Rank dropped 30 spots (#1078 → #1108)

2026-08-30

Rank Moved

Rank dropped 49 spots (#1029 → #1078)

2026-08-29

Rank Moved

Rank dropped 51 spots (#978 → #1029)

2026-08-28

Rank Moved

Rank dropped 35 spots (#943 → #978)

2026-08-27

Rank Moved

Rank dropped 26 spots (#917 → #943)

2026-08-26

Rank Moved

Rank dropped 111 spots (#806 → #917)

2026-08-22

Rank Moved

Rank rose 10 spots (#807 → #797)

2026-08-16

Rank Moved

Rank dropped 15 spots (#794 → #809)

2026-08-13

Rank Moved

Rank dropped 11 spots (#781 → #792)

2026-08-10

Rank Moved

Rank dropped 44 spots (#746 → #790)

2026-08-08

Rank Moved

Rank dropped 316 spots (#427 → #743)

2026-07-29

Rank Moved

Rank dropped 11 spots (#411 → #422)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

MindSearch

How MindSearch could raise its score

Chain of custody

Source Signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How MindSearch compares in Research & Data

Where the 27.5 comes from

HVTrust dimensions vs the Research & Data average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about MindSearch

AI agent surface

Maintain MindSearch?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Research & Data