Is zvec-grep safe to use?

zvec-grep has an HVTrust score of 87.5/100 (Grade A), ranked #67 of 1387 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 87.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.3k 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? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.6 / 10

Provenance Attested

Signed commits 100%

Last push 2d ago

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 87.5/100 (Grade A), ranked #67 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.6/10; 100% of recent commits are signed; no published advisory affects its latest release (@zvec/zvec-grep); last pushed 2026-11-13. 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 from 5.6 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Fuzzing 0 +5.7 → 93.2 A · #1 of 52

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships zvec-grep and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/zvec-ai/zvec-grep, Apache-2.0, last pushed 2026-11-13. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:
- Code Review9
- Branch Protection6
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies1
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 9

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0
Published packages Linked and attested
- npm @zvec/zvec-grep Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @zvec/zvec-grep 0.3.0. No published advisory affects it (OSV, checked 2026-11-14).

Changes to this chain

2026-11-03 Package provenance attestation detected
2026-10-02 OSSF Scorecard: 4.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues zvec-grep’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 zvec-grep compares in Memory & Knowledge

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

Where the 87.5 comes from

HVTrust dimensions vs the Memory & Knowledge average

87.5 / 100 · 100.0% confidence

zvec-grep Memory & Knowledge average (52 agents)

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

19.5 / 25

7.6 above avg 11.9

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.4 above avg 12.6

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

in line with avg 13.0

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

2.8 above avg 17.1

AdoptionLog-scaled stars · package downloads

13.7 / 20

0.6 above avg 13.1

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-03

Provenance Added

Package provenance attestation detected

2026-11-03

Grade Changed

Trust grade B → A

2026-11-03

Rank Moved

Rank rose 219 spots (#290 → #71)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.

Compare with ReMe View Memory & Knowledge Report missing data

83.0

Activity sub-score · out of 100

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 A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars

4.3k

Forks

269

Last Push

2026-11-13

2 days ago

Commits (4 wk)

106

Downloads (7d)

5,629

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #66

Analysis

Activity Inputs

83.0 / 100

StarsRepository reach

21.8 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.3 / 20

Common questions about zvec-grep

Public supply-chain signals for zvec-grep are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but zvec-grep carries less obvious unverified-evidence risk than projects with thin signals.

Does zvec-grep publish package provenance?

Yes. zvec-grep's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does zvec-grep have an OpenSSF Scorecard?

zvec-grep has an OpenSSF Scorecard score of 5.6/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 zvec-grep actively maintained?

Actively maintained. The repository was pushed to within the last 2 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?

100% 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.

Compare zvec-grep head-to-head

zvec-grep vs ReMe → zvec-grep vs EverOS → zvec-grep vs OpenViking →

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

How this surface has changed

Detected changes to zvec-grep'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-11-03

Provenance Added

Package provenance attestation detected

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-11-03

Provenance Added

Package provenance attestation detected

2026-11-03

Grade Changed

Trust grade B → A

2026-11-03

Rank Moved

Rank rose 219 spots (#290 → #71)

2026-11-03

HVTrust Changed

HVTrust up 14.0pts (73.4 → 87.4)

2026-11-02

Rank Moved

Rank rose 10 spots (#300 → #290)

2026-10-29

Rank Moved

Rank rose 19 spots (#328 → #309)

2026-10-22

Rank Moved

Rank rose 29 spots (#363 → #334)

2026-10-13

Rank Moved

Rank rose 13 spots (#376 → #363)

2026-10-09

Rank Moved

Rank dropped 15 spots (#371 → #386)

2026-10-02

Scorecard Added

OSSF Scorecard: 4.7/10

2026-10-02

Grade Changed

Trust grade D → B

2026-10-02

Rank Moved

Rank rose 801 spots (#1160 → #359)

2026-10-02

HVTrust Changed

HVTrust up 28.3pts (40.8 → 69.1)

2026-09-29

Newly Listed

First tracked at rank #1154

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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

zvec-grep

How zvec-grep could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How zvec-grep compares in Memory & Knowledge

Where the 87.5 comes from

HVTrust dimensions vs the Memory & Knowledge average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about zvec-grep

Compare zvec-grep head-to-head

AI agent surface

Maintain zvec-grep?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Memory & Knowledge