@libsql/client No license 70 versions

@libsql/client

npm Repository Homepage

70

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

penberg

Keywords

libsqldatabasesqliteserverlessvercelnetlifylambda

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Long-stable org transfer, not a takeover indicator.	ai	2026/07/21
provenance	publisher-changed-stale	AI (provenance): Publisher change stable for 3+ years, consistent with legitimate transfer.	ai	2026/07/21
publish-pattern	new-deps-added	AI (publish-pattern): js-base64 is a benign, widely-used encoding dependency.	ai	2026/07/21
npm-metadata	suspicious-initial-version	AI (npm-metadata): Legitimate first release of established, widely-used package.	ai	2026/07/21
phantom-deps	phantom-dep:js-base64	AI (phantom-deps): js-base64 is a legitimate declared dependency; phantom-dep flag reflects indirect usage pattern, not a security concern for this package.	ai	2026/04/25

Versions (showing 70 of 70)

Version	Deps	Published
0.17.4	5 / 9	2026-06-15
0.17.3	5 / 9	2026-04-23
0.17.2	5 / 9	2026-03-19
0.17.1	5 / 9	2026-03-19
0.17.0	5 / 9	2026-01-07
0.15.15	5 / 9	2025-09-08
0.15.14	5 / 9	2025-08-26
0.15.13	5 / 9	2025-08-26
0.15.12	5 / 9	2025-08-18
0.15.11	5 / 9	2025-08-14
0.15.10	5 / 9	2025-07-16
0.15.9	5 / 9	2025-06-09
0.15.8	5 / 9	2025-05-30
0.15.7	5 / 9	2025-05-20
0.15.6	5 / 9	2025-05-14
0.15.5	5 / 9	2025-05-11
0.15.4	5 / 9	2025-04-15
0.15.3	5 / 9	2025-04-11
0.15.2	5 / 9	2025-04-01
0.15.1	5 / 9	2025-03-24
0.15.0	5 / 9	2025-03-17
0.14.0	5 / 10	2024-09-20
0.13.0	5 / 10	2024-09-19
0.12.0	5 / 10	2024-09-16
0.11.0	5 / 10	2024-09-13
0.10.0	5 / 10	2024-08-26
0.9.0	5 / 10	2024-08-09
0.8.1	5 / 10	2024-08-03
0.8.0	5 / 10	2024-07-30
0.7.0	5 / 10	2024-06-25
0.6.2	4 / 10	2024-06-01
0.6.1	4 / 10	2024-05-30
0.6.0	4 / 6	2024-03-28
0.5.6	4 / 6	2024-03-12
0.5.5	4 / 6	2024-03-11
0.5.4	4 / 6	2024-03-11
0.5.3	4 / 6	2024-03-06
0.5.2	4 / 6	2024-02-24
0.5.1	4 / 6	2024-02-19
0.5.0	4 / 6	2024-02-15
0.4.3	4 / 6	2024-01-30
0.4.2	4 / 6	2024-01-29
0.4.1	4 / 6	2024-01-29
0.4.0	4 / 6	2024-01-26
0.3.6	3 / 6	2023-10-20
0.3.5	3 / 6	2023-09-25
0.3.4	3 / 7	2023-09-11
0.3.3	3 / 7	2023-09-11
0.3.2	3 / 7	2023-08-29
0.3.1	3 / 7	2023-07-20
0.3.0	3 / 7	2023-07-07
0.2.2	3 / 7	2023-06-22
0.2.1	3 / 7	2023-06-13
0.2.0	3 / 7	2023-06-07
0.1.6	4 / 6	2023-05-12
0.1.5	4 / 6	2023-05-11
0.1.4	4 / 6	2023-04-28
0.1.3	4 / 6	2023-04-24
0.1.2	4 / 6	2023-04-17
0.1.1	4 / 6	2023-03-31
0.1.0	4 / 6	2023-03-30
0.0.9	4 / 6	2023-03-28
0.0.8	3 / 6	2023-03-22
0.0.7	3 / 6	2023-03-02
0.0.5	2 / 6	2023-01-27
0.0.4	2 / 6	2023-01-25
0.0.3	2 / 5	2023-01-20
0.0.2	2 / 4	2023-01-14
0.0.1	2 / 4	2023-01-13
0.0.0	2 / 4	2023-01-12

v0.15.4

1 finding

LOW No provenance attestation provenance

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

v0.15.3

1 finding

LOW No provenance attestation provenance

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

v0.15.2

1 finding

LOW No provenance attestation provenance

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

v0.15.1

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

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.6.2

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.6.1

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.6.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.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

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.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

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: honzasp → penberg (on 2023-09-11, known maintainer) provenance

This version was published by a different npm account (penberg) than the most recent previously approved version (honzasp) on 2023-09-11, but penberg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.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: penberg → honzasp (on 2023-03-30, known maintainer) provenance

This version was published by a different npm account (honzasp) than the most recent previously approved version (penberg) on 2023-03-30, but honzasp is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.9

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: penberg → honzasp (on 2023-03-28, known maintainer) provenance

This version was published by a different npm account (honzasp) than the most recent previously approved version (penberg) on 2023-03-28, but honzasp is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

2 findings

MEDIUM Publisher changed: penberg → just_one_more_time (on 2023-03-02, unremoved on npm for 1236d) provenance

This version was published by a different npm account (just_one_more_time) than the most recent previously approved version (penberg) on 2023-03-02. It has since remained available on npm for 1236 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.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.

v0.0.2

1 finding

LOW No provenance attestation provenance

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

v0.0.1

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.0.0

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.