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. Full methodology →
Signals refreshed2026-06-17 12:03 UTC·Repo last pushed today
Activity & Reach
Stars
10.7k
Forks
619
Last Push
2026-06-17
today
Commits (4 wk)
57
Downloads (7d)
6,652
npm+pypi
HN mentions (30d)
103
Open Issues
57
Rank Change
NEW
Analysis
HVTrust Dimensions
43.6 / 100 · 75.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.0 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
19.0 / 20
AdoptionStars and downloads
14.8 / 20
Activity Inputs
84.2 / 100
StarsRepository reach
24.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.0 / 25
CommunityFork signal
13.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
100%
of last 100 commits verified
Is Zvec safe?
Public trust evidence for Zvec 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 publish package provenance?
No published build provenance is currently detected for Zvec. 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 have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Zvec. 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 actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Zvec use?
Zvec ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Zvec's commits signed?
100% of the last 100 commits to Zvec 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
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Postgres
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
database
search
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Warning
1 package source mismatch detected
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?
HVTrust scores Zvec 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.
