Is Milvus safe to use?

Milvus has an HVTrust score of 72.4/100 (Grade B), ranked #114 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Milvus?

Milvus scores 72.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 45.6k GitHub stars and is categorized under Memory & Knowledge.

Milvus

milvus-io/milvus

Milvus is a high-performance, cloud-native vector database built for scalable vector ANN search

Memory & Knowledge Go Grade B Listed Apache-2.0

72.4/100

Rank #114 of 1283

Compare Milvus

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-15 · 0d ago

Recent change

No recent signal change

Is Milvus safe? Milvus scores 72.4/100 (Grade B), ranked #114 of 1283 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 100% of recent commits are signed; last pushed 2026-08-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#10 Chroma — 74.4 (B) → #11 GraphRAG — 73.0 (B) → #13 RAGFlow — 72.1 (B) → #14 Tidb — 71.5 (B) →

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 4.3/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.

Compare with another agent Get email alerts for Milvus View Memory & Knowledge Report missing data

94.8

Activity sub-score · out of 100

#12

In Memory & Knowledge

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars

45.6k

Forks

4.2k

Last Push

2026-08-15

today

Commits (4 wk)

241

Downloads (7d)

1,313,319

pypi

HN mentions (30d)

Open Issues

938

Rank Change

was #114

Analysis

HVTrust Dimensions vs Memory & Knowledge

72.4 / 100 · 100.0% confidence

Milvus Memory & Knowledge average (42 agents)

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

10.4 / 25

in line with avg 10.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.5

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

2.3 above avg 17.7

AdoptionLog-scaled stars · package downloads

19.3 / 20

5.7 above avg 13.6

Activity Inputs

94.8 / 100

StarsRepository reach

28.0 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

16.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Aug 15, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 5

Code-Review 10

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Milvus safe?

Milvus has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Milvus publish package provenance?

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

Does Milvus have an OpenSSF Scorecard?

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

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

What license does Milvus use?

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

Are Milvus's commits signed?

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

None detected

No clear third-party provider dependency detected.

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Milvus?

For maintainers

HVTrust scores Milvus 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-07-13

Rank Moved

Rank dropped 11 spots (#72 → #83)

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (58.5 → 68.5)

2026-05-27

Grade Changed

Trust grade C → B

2026-05-27

Rank Moved

Rank rose 27 spots (#36 → #9)

2026-05-27

HVTrust Changed

HVTrust up 26.9pts (38.8 → 65.7)

2026-05-27

Activity Score Changed

Activity score up 25pts (70 → 95)

2026-05-26

Rank Moved

Rank dropped 28 spots (#8 → #36)

2026-05-26

Activity Score Changed

Activity score down 25pts (95 → 70)

2026-05-25

Newly Listed

First tracked at rank #8

GitHub → PyPI: pymilvus

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON