updated 2026-08-09 19:31 UTC

Vespa

vespa-engine/vespa

The AI search platform

Memory & Knowledge Java Grade A Listed Apache-2.0
86.2/100
Rank #37 of 1204
Compare Vespa

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

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade A · 4/5 signals
Last push
2026-08-08 · 1d ago
Recent change
No recent signal change

Is Vespa safe? Vespa scores 86.2/100 (Grade A), ranked #37 of 1204 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.8/10; 56% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#1 LanceDB — 87.1 (A) → #3 Mem0 — 86.1 (A) → #4 Graphiti — 85.9 (A) → #5 LightRAG — 84.1 (A) →

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.
Compare with LanceDB Get email alerts for Vespa View Memory & Knowledge Report missing data
86.3
Activity sub-score · out of 100
#2
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 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 →

Signals refreshed 2026-08-09 19:31 UTC · Repo last pushed yesterday

Activity & Reach

Stars
7.0k
Forks
730
Last Push
2026-08-08
yesterday
Commits (4 wk)
205
Downloads (7d)
2,314,073
pypi
HN mentions (30d)
0
Open Issues
223
Rank Change
▼1
was #36

Analysis

HVTrust Dimensions vs Memory & Knowledge

86.2 / 100 · 100.0% confidence

Vespa Memory & Knowledge average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.5 / 25
6.9 above avg 10.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.7 above avg 12.3
Transparency50% declared license · 50% OSSF Scorecard
13.4 / 17
0.7 above avg 12.7
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
2.4 above avg 17.5
AdoptionLog-scaled stars · package downloads
17.7 / 20
3.6 above avg 14.1

Activity Inputs

86.3 / 100
StarsRepository reach
23.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.3 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.8 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
56%
of last 100 commits verified
Binary-Artifacts 9
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 10
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 1
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Vespa safe?

Public supply-chain signals for Vespa are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Vespa carries less obvious unverified-evidence risk than projects with thin signals.
Does Vespa publish package provenance?
Yes. Vespa's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Vespa have an OpenSSF Scorecard?
Vespa has an OpenSSF Scorecard score of 5.8/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 Vespa actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Vespa use?
Vespa ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Vespa's commits signed?
56% of the last 100 commits to Vespa 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 Vespa head-to-head

Vespa vs LanceDB → Vespa vs Mem0 → Vespa vs Graphiti →

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
How this surface has changed

Detected changes to Vespa'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-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared

Maintain Vespa?

For maintainers

HVTrust scores Vespa 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
Rank 3Score 2Listed 1HVTrust 1Grade 1Surface 1
2026-06-05
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-05-29
Rank Moved
Rank dropped 10 spots (#4 → #14)
2026-05-27
Grade Changed
Trust grade C → B
2026-05-27
Rank Moved
Rank rose 87 spots (#101 → #14)
2026-05-27
HVTrust Changed
HVTrust up 37.6pts (45.7 → 83.3)
2026-05-27
Activity Score Changed
Activity score up 25pts (61 → 86)
2026-05-26
Rank Moved
Rank dropped 87 spots (#14 → #101)
2026-05-26
Activity Score Changed
Activity score down 25pts (86 → 61)
2026-05-25
Newly Listed
First tracked at rank #14
GitHub → PyPI: pyvespa

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 86.2 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/vespa.svg)](https://hvtracker.net/agents/vespa)
HTML:
<a href="https://hvtracker.net/agents/vespa"><img src="https://hvtracker.net/badge/vespa.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.2 · Raw JSON