updated 2026-10-09 16:07 UTC

LanceDB

Repository Website

Developer-friendly OSS embedded retrieval library for multimodal AI. Search More; Manage Less.

Memory & Knowledge Rust Listed Apache-2.0

Is LanceDB safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.2 / 10
Provenance Attested
Signed commits 88%
Last push today
Advisories None known
Compare LanceDB

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

Pick any agent to compare →
Suggest a correction

In detail: LanceDB scores 87.8/100 (Grade A), ranked #44 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 6.2/10; 88% of recent commits are signed; no published advisory affects its latest release (lancedb); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How LanceDB 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships LanceDB 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.

  1. Source Signed

    github.com/lancedb/lancedb, Apache-2.0, last pushed 2026-10-09. 88% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.2/10 (scanned Oct 5, 2026). The checks that decide who can get a change released:

    • Code Review9
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 9
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 8
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Partly attested

    • PyPI lancedb Source link isn't a GitHub repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: lancedb 0.40.0. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-10-08 Package provenance attestation detected
  • 2026-09-23 Package provenance attestation no longer detected
  • 2026-09-18 Package provenance attestation detected
  • 2026-09-02 Package provenance attestation no longer detected

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 LanceDB’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 LanceDB compares in Memory & Knowledge

  1. #1 ReMe 88.8 +1.0
  2. #2 OpenViking 88.2 +0.4
  3. #3 LanceDB 87.8 this agent
  4. #4 Graphiti 87.2 −0.6
  5. #5 Mem0 86.1 −1.7

Bars show each HVTrust score; the tick marks LanceDB’s 87.8.

Where the 87.8 comes from

HVTrust dimensions vs the Memory & Knowledge average

87.8 / 100 · 100.0% confidence

LanceDB Memory & Knowledge average (49 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.7 / 25
8.4 above avg 11.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.4 above avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
1.2 above avg 12.6
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
2.6 above avg 17.4
AdoptionLog-scaled stars · package downloads
18.1 / 20
4.9 above avg 13.2

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-10-08
Provenance Added
Package provenance attestation detected
2026-10-08
Grade Changed
Trust grade B → A
2026-10-08
Rank Moved
Rank rose 230 spots (#274 → #44)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.
Compare with ReMe Get email alerts for LanceDB View Memory & Knowledge Report missing data
88.5
Activity sub-score · out of 100
#3
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-10-09 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
11.6k
Forks
1.1k
Last Push
2026-10-09
today
Commits (4 wk)
163
Downloads (7d)
1,786,298
pypi
HN mentions (30d)
19
Open Issues
509
Rank Change
=
was #44

Analysis

Activity Inputs

88.5 / 100
StarsRepository reach
24.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.1 / 20

Common questions about LanceDB

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

LanceDB vs ReMe → LanceDB vs OpenViking → LanceDB 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
high confidence
4 detected
Public provider/service dependencies 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 LanceDB'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-10-08
Provenance Added
Package provenance attestation detected
2026-09-23
Provenance Removed
Package provenance attestation no longer detected
2026-09-18
Provenance Added
Package provenance attestation detected
2026-09-02
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-09-02
Provenance Removed
Package provenance attestation no longer detected

Maintain LanceDB?

For maintainers

HVTrust scores LanceDB 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 7HVTrust 4Grade 4Provenance 2Provenance 2Surface 1
2026-10-08
Provenance Added
Package provenance attestation detected
2026-10-08
Grade Changed
Trust grade B → A
2026-10-08
Rank Moved
Rank rose 230 spots (#274 → #44)
2026-10-08
HVTrust Changed
HVTrust up 14.9pts (72.9 → 87.8)
2026-09-23
Provenance Removed
Package provenance attestation no longer detected
2026-09-23
Grade Changed
Trust grade A → B
2026-09-23
Rank Moved
Rank dropped 246 spots (#38 → #284)
2026-09-23
HVTrust Changed
HVTrust down 14.5pts (86.8 → 72.3)
2026-09-21
Rank Moved
Rank rose 12 spots (#51 → #39)
2026-09-18
Provenance Added
Package provenance attestation detected
2026-09-18
Grade Changed
Trust grade B → A
2026-09-18
Rank Moved
Rank rose 234 spots (#288 → #54)
2026-09-18
HVTrust Changed
HVTrust up 14.9pts (72.0 → 86.9)
2026-09-07
Rank Moved
Rank dropped 20 spots (#247 → #267)
2026-09-05
Rank Moved
Rank dropped 53 spots (#186 → #239)
2026-09-02
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-09-02
Provenance Removed
Package provenance attestation no longer detected
2026-09-02
Grade Changed
Trust grade A → B
2026-09-02
Rank Moved
Rank dropped 138 spots (#35 → #173)
2026-09-02
HVTrust Changed
HVTrust down 14.3pts (86.8 → 72.5)
GitHub → Website → PyPI: lancedb

Embed Badge Badge guide for maintainers →

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