Vespa
Website
The AI search platform
Is Vespa safe? Strong public trust posture, backed by multiple independent signals.
Compare Vespa
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: Vespa scores 85.3/100 (Grade A), ranked #86 of 1371 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; 64% of recent commits are signed; last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How Vespa 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.8 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +6.7 → 92.0 A · #1 of 49
- Sign every commit64% signed today +1.9 → 87.2 A · #4 of 49
Chain of custody
Scanners check what the code says. This traces who ships Vespa 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 Partly signed
github.com/vespa-engine/vespa, Apache-2.0, last pushed 2026-10-09. 64% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.8/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies2
All 14 Scorecard checks
Binary-Artifacts 9Branch-Protection 5CII-Best-Practices 0Code-Review 10Dangerous-Workflow 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 2SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0 -
Published packages Partly attested
- PyPI pyvespa Source link isn't a GitHub repo Build provenance attested
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Vespa.
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Vespa’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.
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 Vespa compares in Memory & Knowledge
- #6 Hindsight 86.1 +0.8
- #7 Cognee 85.8 +0.5
- #8 Vespa 85.3 this agent
- #9 LightRAG 85.2 −0.1
- #10 EverOS 85.0 −0.3
Bars show each HVTrust score; the tick marks Vespa’s 85.3.
Where the 85.3 comes from
HVTrust dimensions vs the Memory & Knowledge average
85.3 / 100 · 100.0% confidenceVespa Memory & Knowledge average (49 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
86.5 / 100Common questions about Vespa
Does Vespa publish package provenance?
Does Vespa have an OpenSSF Scorecard?
Is Vespa actively maintained?
What license does Vespa use?
Are Vespa's commits signed?
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
AI agent surface
MCP, providers, tool surface
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/vespa)
<a href="https://hvtracker.net/agents/vespa"><img src="https://hvtracker.net/badge/vespa.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
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.4 · Raw JSON