@splendidlabz/db
Usage with Astro DB
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Private scoped package under @splendidlabz namespace; sparse metadata is expected for internal tooling. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; missing description is consistent across the @splendidlabz namespace. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped org package @splendidlabz/db; not a typosquat of pg — edit distance match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped org package @splendidlabz/db; not a typosquat of qs — edit distance match is coincidental. | ai | |
| phantom-deps | phantom-dep:oslo | AI (phantom-deps): oslo is a declared dependency used via config/indirect reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@libsql/client | AI (phantom-deps): @libsql/client declared dependency used via config/indirect reference; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 4 / 3 | |
| 1.4.0 | 4 / 3 | |
| 1.3.0 | 4 / 3 | |
| 1.2.0 | 4 / 3 | |
| 1.1.0 | 4 / 3 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.