@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 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.17.4 | 1 / 6 | |
| 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 | |
| 0.15.4 | 1 / 6 | |
| 0.15.3 | 1 / 6 | |
| 0.15.2 | 1 / 6 | |
| 0.15.1 | 1 / 6 | |
| 0.15.0 | 1 / 6 | |
| 0.14.0 | 1 / 6 | |
| 0.13.0 | 1 / 6 | |
| 0.12.0 | 1 / 6 | |
| 0.11.0 | 1 / 6 | |
| 0.10.0 | 1 / 6 | |
| 0.9.0 | 1 / 6 | |
| 0.8.1 | 1 / 6 | |
| 0.8.0 | 1 / 6 | |
| 0.7.0 | 1 / 6 | |
| 0.6.2 | 1 / 6 | |
| 0.6.1 | 1 / 6 | |
| 0.6.0 | 1 / 6 | |
| 0.5.6 | 1 / 6 | |
| 0.5.5 | 1 / 6 | |
| 0.5.4 | 1 / 6 | |
| 0.5.3 | 1 / 6 | |
| 0.5.2 | 1 / 6 | |
| 0.5.1 | 1 / 6 | |
| 0.5.0 | 1 / 6 | |
| 0.4.3 | 1 / 6 | |
| 0.4.2 | 1 / 6 | |
| 0.4.1 | 1 / 6 | |
| 0.4.0 | 1 / 6 |
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.