@lancedb/lancedb — Greenflagged

LanceDB: A serverless, low-latency vector database for AI applications

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

changhiskhanwestonpacejackye1995wjones127eddyxu

Keywords

databaselancelancedbsearchvectorvector databaseann

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-execsync	AI (semgrep): execSync('which ldd') is used to detect musl libc for native binary selection — standard NAPI pattern, not malicious.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): child_process import is solely for ldd detection in native binary loading; benign and expected for this NAPI package.	ai	2026/04/24
source-diff	net-exec-file:dist/embedding/transformers.js	AI (source-diff): This file is a compiled TypeScript embedding integration for @xenova/transformers ML models. Network calls download model weights; 'execution' is model inference. Standard, documented behavior for a vector DB embedding module. No obfuscation or malicious patterns.	ai	2026/04/24
license	uncommon-license:Apache 2.0	AI (license): Apache 2.0 is a well-known permissive license; the analyzer flags it due to non-canonical string formatting vs 'Apache-2.0'. Stable false positive for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): LanceDB migrated to GitHub Actions CI/CD publishing with SLSA provenance attestation — a legitimate and security-positive transition for this established package.	ai	2026/04/23
provenance	slsa-provenance	AI (provenance): Package has SLSA provenance via Sigstore; this is the expected publishing pattern for this package going forward.	ai	2026/04/23

Versions (showing 43 of 43)

Version	Deps	Published
0.27.2	1 / 23	2026-03-31
0.27.1	1 / 23	2026-03-20
0.27.0	1 / 23	2026-03-16
0.26.2	1 / 23	2026-02-09
0.24.1	1 / 23	2026-02-04
0.23.0	1 / 23	2025-12-16
0.22.3	1 / 23	2025-11-07
0.22.2	1 / 23	2025-10-08
0.22.1	1 / 23	2025-09-24
0.22.0	1 / 23	2025-09-04
0.21.3	1 / 23	2025-08-15
0.21.2	1 / 23	2025-07-25
0.21.1	1 / 23	2025-07-10
0.21.0	1 / 23	2025-06-20
0.20.0	1 / 23	2025-06-04
0.19.1	1 / 23	2025-05-22
0.19.0	1 / 23	2025-04-25
0.18.2	1 / 23	2025-03-26
0.18.1	1 / 23	2025-03-11
0.18.0	1 / 23	2025-03-11
0.17.0	1 / 23	2025-02-26
0.16.0	1 / 23	2025-02-07
0.15.0	1 / 23	2025-01-14
0.14.1	1 / 23	2024-12-26
0.14.0	1 / 24	2024-12-06
0.13.0	1 / 24	2024-11-15
0.12.0	1 / 24	2024-10-29
0.11.0	1 / 24	2024-10-09
0.10.0	2 / 23	2024-09-10
0.9.0	2 / 23	2024-08-07
0.8.0	2 / 23	2024-08-02
0.7.1	2 / 19	2024-07-17
0.7.0	2 / 19	2024-07-13
0.5.2	3 / 17	2024-06-05
0.5.1	3 / 17	2024-05-30
0.5.0	2 / 17	2024-05-23
0.4.20	2 / 20	2024-05-09
0.4.19	2 / 20	2024-05-07
0.4.18	2 / 20	2024-04-30
0.4.16	2 / 18	2024-04-05
0.4.15	2 / 18	2024-04-02
0.4.13	2 / 18	2024-03-27
0.4.3	1 / 18	2024-03-24

v0.27.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.27.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.27.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.26.2

2 findings

HIGH Publisher changed: westonpace → GitHub Actions (on 2026-02-09) provenance

This version was published by a different npm account than previous versions on 2026-02-09. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.24.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: wjones127 → westonpace (on 2026-02-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: westonpace → wjones127 (on 2024-10-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-09. This could indicate a legitimate maintainer transition or an account compromise.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: wjones127 → westonpace (on 2024-08-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-08-07. This could indicate a legitimate maintainer transition or an account compromise.

v0.8.0

3 findings

HIGH New file with network + code execution: dist/embedding/transformers.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: westonpace → wjones127 (on 2024-08-02) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-08-02. This could indicate a legitimate maintainer transition or an account compromise.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.