Is zvec-grep safe to use?

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

What is the trust score for zvec-grep?

zvec-grep scores 40.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.8k GitHub stars and is categorized under Memory & Knowledge.

zvec-grep

Repository

Local-first search across your workspace, built for humans and AI agents.

Memory & Knowledge Rust Listed Apache-2.0

Is zvec-grep safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result

Provenance None

Signed commits 72%

Last push yesterday

Advisories None known

Compare zvec-grep

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

Pick any agent to compare →

Suggest a correction

In detail: zvec-grep scores 40.9/100 (Grade D), ranked #1152 of 1343 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 72% of recent commits are signed; no published advisory affects its latest release (@zvec/zvec-grep); last pushed 2026-09-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How zvec-grep 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 +37.2 → 78.1 B · #10 of 45
Publish build provenance for its packagesnpm publish --provenance from CI +33.1 → 74.0 B · #14 of 45
Sign every commit72% signed today +0.9 → 41.8 D · #45 of 45

Already done? Suggest a correction Add the trust badge

How zvec-grep compares in Memory & Knowledge

Bars show each HVTrust score; the tick marks zvec-grep’s 40.9.

Where the 40.9 comes from

HVTrust dimensions vs the Memory & Knowledge average

40.9 / 100 · 67.0% confidence

zvec-grep Memory & Knowledge average (45 agents)

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

3.6 / 25

8.2 below avg 11.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.8 below avg 12.6

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

4.4 below avg 12.9

Maintenance60% last-push freshness · 40% commit activity

19.3 / 20

2.1 above avg 17.2

AdoptionLog-scaled stars · package downloads

13.1 / 20

0.5 below avg 13.6

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

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 zvec-grep View Memory & Knowledge Report missing data

80.2

Activity sub-score · out of 100

#45

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

Activity & Reach

Stars

3.8k

Forks

223

Last Push

2026-09-28

yesterday

Commits (4 wk)

Downloads (7d)

2,572

npm

HN mentions (30d)

—

Open Issues

Rank Change

NEW

Analysis

Activity Inputs

80.2 / 100

StarsRepository reach

21.5 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.9 / 25

CommunityFork signal

10.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

72%

of last 100 commits verified

Common questions about zvec-grep

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

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

Does zvec-grep have an OpenSSF Scorecard?

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

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

What license does zvec-grep use?

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

Are zvec-grep's commits signed?

72% of the last 100 commits to zvec-grep 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

medium confidence

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Multi-provider (LiteLLM)

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

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

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

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

Maintain zvec-grep?

For maintainers

HVTrust scores zvec-grep 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 #1152

GitHub → npm: @zvec/zvec-grep

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Memory & Knowledge

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