@atscript/db
Database adapter utilities for atscript.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| — | large-new-source-files | — | sean | |
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs 'asc -f dts' — atscript CLI for DTS generation; stable pattern for this toolchain package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @atscript/db; Levenshtein match to 'pg' is a false positive given the namespace and description. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @atscript/db; Levenshtein match to 'qs' is a false positive given the namespace and description. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.63 | 0 / 4 | |
| 0.1.51 | 0 / 4 | |
| 0.1.40 | 0 / 4 | |
| 0.1.39 | 0 / 1 | |
| 0.1.38 | 0 / 1 |
v0.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
2 findingsScript: asc -f dts
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.