@astrojs/db
Add libSQL support to your Astro site
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@astrojs/studio | AI (dependencies): First-party withastro org package, part of documented Astro DB/Studio feature. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Same first-party dependency addition, expected for this integration. | ai | |
| phantom-deps | phantom-dep:ci-info | AI (phantom-deps): Used indirectly via config, common pattern, not a real risk. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Official withastro scoped package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Official withastro scoped package; Levenshtein match to 'qs' is a false positive. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.21.3 | 8 / 7 | |
| 0.21.2 | 8 / 7 | |
| 0.21.1 | 8 / 7 | |
| 0.21.0 | 8 / 7 | |
| 0.20.1 | 8 / 7 | |
| 0.20.0 | 8 / 8 | |
| 0.19.0 | 8 / 9 | |
| 0.18.3 | 8 / 9 | |
| 0.18.2 | 8 / 9 | |
| 0.18.1 | 8 / 9 | |
| 0.18.0 | 8 / 9 | |
| 0.17.2 | 8 / 9 | |
| 0.17.1 | 8 / 9 | |
| 0.17.0 | 8 / 8 | |
| 0.16.1 | 8 / 8 | |
| 0.16.0 | 8 / 8 | |
| 0.15.1 | 13 / 8 | |
| 0.15.0 | 13 / 8 | |
| 0.14.14 | 13 / 8 | |
| 0.14.13 | 13 / 8 | |
| 0.14.12 | 13 / 8 | |
| 0.14.11 | 13 / 8 | |
| 0.14.10 | 13 / 8 | |
| 0.14.9 | 13 / 8 | |
| 0.14.8 | 13 / 8 | |
| 0.14.7 | 13 / 8 | |
| 0.14.6 | 13 / 8 | |
| 0.14.5 | 13 / 8 | |
| 0.14.4 | 13 / 8 | |
| 0.14.3 | 13 / 8 | |
| 0.14.2 | 13 / 8 | |
| 0.14.1 | 14 / 8 | |
| 0.14.0 | 14 / 8 | |
| 0.13.2 | 14 / 8 | |
| 0.13.1 | 14 / 8 | |
| 0.13.0 | 13 / 7 | |
| 0.12.0 | 15 / 10 | |
| 0.11.7 | 15 / 10 | |
| 0.11.6 | 15 / 10 | |
| 0.11.5 | 15 / 10 | |
| 0.11.4 | 15 / 13 | |
| 0.11.3 | 15 / 13 | |
| 0.11.2 | 14 / 13 | |
| 0.11.1 | 14 / 13 | |
| 0.11.0 | 14 / 13 | |
| 0.10.7 | 14 / 13 |
v0.18.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (matthewp) on 2025-10-23, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
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.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (matthewp) than the most recent previously approved version (fredkschott) on 2025-03-26, but matthewp 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.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.