Is Jevgrep safe to use?

Jevgrep is newly listed and still being checked: its HVTrust score is provisional until the first full signal fetch completes, so no grade has been assigned yet.

What is the trust score for Jevgrep?

Jevgrep scores 0.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 0 GitHub stars and is categorized under Protocols & Tool Integration.

Jevgrep

Repository by dzhng

Protocols & Tool Integration Listed

Evidence is still being collected. Jevgrep hasn't had its first full check yet: 0 of the 5 signals its score is built from are in (still to fetch: GitHub activity, OSSF Scorecard, package downloads, provenance and signed commits), so the score is provisional and no grade is shown.

GitHub activity pending

OSSF Scorecard pending

Package downloads pending

Provenance pending

Signed commits pending

Compare Jevgrep

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Suggest a correction

How Jevgrep compares in Protocols & Tool Integration

Bars show each HVTrust score; the tick marks Jevgrep’s 0.0.

Where the 0.0 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

0.0 / 100 · provisional

Jevgrep Protocols & Tool Integration average (63 agents)

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

0 / 25

10.8 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.0 below avg 11.8

Transparency50% declared license · 50% OSSF Scorecard

0 / 17

12.8 below avg 12.8

Maintenance60% last-push freshness · 40% commit activity

0 / 20

13.9 below avg 13.9

AdoptionLog-scaled stars · package downloads

0 / 20

10.9 below avg 10.9

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-10-15

Newly Listed

First tracked at rank #1376

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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

Compare with another agent Get email alerts for Jevgrep View Protocols & Tool Integration Report missing data

0.0

Activity sub-score · out of 100

#63

In Protocols & Tool Integration

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

Forks

Last Push

pending

999 days ago

Commits (4 wk)

—

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

—

Analysis

Activity Inputs

0.0 / 100

StarsRepository reach

0.0 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

0.0 / 20

Common questions about Jevgrep

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

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

Does Jevgrep have an OpenSSF Scorecard?

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

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

What license does Jevgrep use?

Jevgrep ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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

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 Jevgrep?

For maintainers

HVTrust scores Jevgrep 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-15

Newly Listed

First tracked at rank #1376

GitHub → npm: @dzhng/jevgrep

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Protocols & Tool Integration

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