@libsql/hrana-client MIT 39 versions

@libsql/hrana-client

npm Repository Homepage

Hrana client for connecting to sqld over HTTP or WebSocket

39

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

penberg

Keywords

hranalibsqlsqlddatabase

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:node-fetch	AI (phantom-deps): node-fetch is a transitive fetch polyfill dependency, referenced via config not direct import.	ai	2026/07/08
dependencies	unvetted-dep:@libsql/isomorphic-fetch	AI (dependencies): First-party libsql org package, standard dependency for this client library.	ai	2026/07/08
dependencies	unvetted-dep:@libsql/isomorphic-ws	AI (dependencies): Sibling package within the @libsql namespace; a natural WebSocket abstraction dependency for this database client. Stable across all versions.	ai	2026/04/25

Versions (showing 39 of 39)

Version	Deps	Published
0.10.0	2 / 4	2026-04-22
0.9.0	4 / 5	2025-12-26
0.8.0	4 / 5	2024-09-19
0.7.0	4 / 5	2024-09-16
0.6.2	4 / 5	2024-06-03
0.6.1	4 / 5	2024-06-03
0.6.0	4 / 5	2024-03-28
0.5.6	4 / 5	2024-01-26
0.5.5	4 / 5	2023-09-18
0.5.4	3 / 5	2023-09-18
0.5.3	3 / 5	2023-09-18
0.5.2	3 / 5	2023-09-11
0.5.1	3 / 5	2023-09-11
0.5.0	3 / 5	2023-08-29
0.4.4	3 / 5	2023-08-15
0.4.3	3 / 5	2023-07-18
0.4.2	3 / 5	2023-06-22
0.4.1	3 / 5	2023-06-12
0.4.0	3 / 5	2023-06-07
0.3.13	2 / 5	2023-05-16
0.3.12	2 / 5	2023-05-16
0.3.11	2 / 5	2023-05-14
0.3.10	2 / 5	2023-05-11
0.3.9	2 / 5	2023-04-28
0.3.8	2 / 5	2023-04-26
0.3.7	2 / 5	2023-04-25
0.3.6	2 / 5	2023-04-24
0.3.5	2 / 5	2023-04-17
0.3.4	2 / 5	2023-04-12
0.3.3	2 / 5	2023-03-30
0.3.2	3 / 5	2023-03-29
0.3.1	3 / 5	2023-03-28
0.3.0	3 / 5	2023-03-28
0.2.0	3 / 4	2023-03-13
0.1.4	3 / 4	2023-03-07
0.1.3	2 / 4	2023-03-02
0.1.2	1 / 5	2023-03-02
0.1.1	1 / 5	2023-03-01
0.1.0	1 / 5	2023-03-01

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

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

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.5.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: 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.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.4

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

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

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

1 finding

LOW No provenance attestation provenance

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

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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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