@libsql/core
libSQL driver for TypeScript and JavaScript
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from penberg to GitHub Actions as part of a legitimate migration to CI/CD publishing with SLSA provenance attestation. This is a supply chain improvement, not a compromise. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @libsql/core is the legitimate core library for the libSQL/Turso database client, not a typosquat of 'cors'. The name similarity is purely coincidental (core vs cors). | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.17.3 | 1 / 6 | |
| 0.17.2 | 1 / 6 | |
| 0.17.1 | 1 / 6 | |
| 0.17.0 | 1 / 6 | |
| 0.16.0 | 1 / 6 | |
| 0.15.15 | 1 / 6 | |
| 0.15.14 | 1 / 6 | |
| 0.15.13 | 1 / 6 | |
| 0.15.12 | 1 / 6 | |
| 0.15.11 | 1 / 6 | |
| 0.15.10 | 1 / 6 | |
| 0.15.9 | 1 / 6 | |
| 0.15.8 | 1 / 6 | |
| 0.15.7 | 1 / 6 | |
| 0.15.6 | 1 / 6 | |
| 0.15.5 | 1 / 6 |
v0.17.3
2 findingsPackage name '@libsql/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.